Вы находитесь на странице: 1из 1

Software Testing process in companies

Whenever we get any new project we will conduct Kick -Off Meeting (introduces the members of the project team and the client and provides the opportunity to discuss the role of each team member). In this meeting we basically discuss on who is client? What is project duration and when is delivery? Who is involved in project i.e manager, Tech leads, QA leads, developers, testers etc etc..? (Initially Business Analyst (BA) will prepare the BRS (Business requirement specification).SRS(system requirement specification) derived from BRS. FRS (Functional requirement specification) derived from SRS .Based on FRS Usecase or test scenarios are developed on this Testers will create the Testcases) Based on the SRS project plan is developed. The responsibility of testers is to create software test plan from this SRS and project plan. Developers start coding from the design. The project work is divided into different modules and these project modules are distributed among the developers. In meantime testers responsibility is to create test scenario and write test cases according to assigned modules. Testers try to cover almost all the functional test cases from SRS/FRS. The Testcases can be maintained manually in some excel test case templates or bug tracking tools like Quality Center (QC). When developers finish individual modules (build), those modules are assigned to testers. Testers will perform Smoke testing (verifying the build URLs for testing means stability of URLs) or Sanity Testing(build is stable is or not for further testing ,here tester will verify the basic functionality) on these modules and if they fail this test, modules(build) are reassigned to respective developers for fix. For passed modules manual testing is carried out from the written test cases. If any bug is found that get assigned to module developer and get logged in bug tracking tool. On bug fix tester do bug verification and regression testing of all related modules. If bug passes the verification it is marked as verified and marked as closed. Otherwise above mentioned bug cycle gets repeated. (I will cover bug life cycle in other post) If it is required as per SRS, tester will test Compatibility testing i.e testing application on different hardware, OS versions, software platform, different browsers etc.
Defect/Bug Life Cycle

Defect:Mismatch between the expected result and Actual result Defect/Bug Life Cycle: When ever we raise a defect status will be "NEW".After raising the defect Testlead/Defect Manager verify the defect and change the status "NEW" to "OPEN". Then delevopment lead will assign the defect to developer and change the status OPEN to "ASSIGN". Developer will verify the defect If it is working fine ,he will "REJECT " the defect.If it postponed to future release the status will be "DEFFERED". If it is not working then he will FIX the Defect,the status will be "FIXED". Once the developer fix the defect testlead will change the status FIXED to "RETEST" Once it is in RETEST we will Retest the defect,if it is working fine ,we will "CLOSE" the defect.else we will "RE OPEN" the defect