User:Suresh Gottimukkala

Before writing a Test plan first as a part of QA Team we need to sit along with the application sponsor and the development team and need to know the application from the scratch. Following are the very basic questions which we need to ask for the client/Dev team before starting up your Test Plan:

• What’s the application expected to do? • What’s a typical expected user experience? (positive and negative) • What’s the application architecture? • What’s the expected traffic volume in terms of unique, concurrent users? • Will the traffic be dependent on time of day? • What type of data will be downloaded from the site and from where? (text only, images, a web service?) • How will the application’s functions influence performance? (i.e., the viewing of images, interactive web service functions, etc.) • What’s the profile of the expected user? Company employee with high-speed access or a home user with an older OS, browser and dial-up connection? • Will the application be hosted on a company intranet or accessed via the Internet? • What and who in the test/QA and development group will handle the security issues and testing? 3 • What is the current development status of the application and the new builds schedule? This directly affects the test plan schedule. • What’s the application’s release schedule? • When will the development team train the QA and test team on the application’s specifics? This is key to understanding the application and leads to better troubleshooting, faster problem solving and improves communication with the development team. Will be continued soon