Project Initiation In general, software development process starts with information gathering and analysis. In this stage business analyst category people are developing BRS and S/W RS like documents. BRS defines requirements of the customer & S/W RS defines functional requirements to be developed and system requirements to be used.
Test Initiation After finalization of requirement document, at this stage test engineers go through the document, understand the functionality and also have formal demo from business analyst. Afterwards if any clarification need on the functionality, they interact with business analyst through various communication channels such mails, calls, requirement Q & A doc, WebEx meetings etc. Test lead will get broad idea what tests to be applied and identify scope of items to be tested.
Test Planning After finalization of possible tests to be applied for corresponding project, test lead category people concentrate on test plan document preparation to define work allocation in terms of “ what to test?”, “Who to test ?”, “when to test ?”, and “How to test ?”.
Review Test Plan After completion of plan document preparation test plan author conducts a review for completeness and correctness. In this review plan author follows “Coverage Analysis” ØBR based coverage (What to test? Review) ØRisks Based coverage (When and Who to test? Review)Test Design After completion of test planning and required training to testing team, corresponding testing team members will prepare list of test cases for their responsible modules. There are three types of test case design methods to cover core level testing. Refer test design techniques and tools page.
Review Test Cases After completion of all possible test cases writing for responsible modules, testing team concentrates on review of test cases for completeness and correctness. In this review testing team applies coverage analysis.
At the end of this review test lead or testing team prepare “Requirements Traceability Matrix” or “Requirements Validation Matrix".
Test Execution After completion of test cases selection & their review, testing team concentrates on build release from development and test execution on the build.
Level 1(Sanity Testing) As soon as testing team receives the build from development, team will execute core functionality test cases and ensure that build is ok to do further test case execution.
Level 2….(Functional Testing)
Last Level (Regression Testing) During comprehensive test execution, test engineers are reporting mismatches as defects to developers. After receiving modified build from them, test engineers concentrate on regression testing to ensure bug fixing work and occurrences of side effects. And also execute set of test cases were identified under test case design phase to ensure the build functionally works very well.
Test Reporting During comprehensive testing, test engineers are reporting mismatches as defects to developers through defect template format or log the defects through defect tracking system
Defect Resolution Type After receiving defect reports from testers, developers reviews that defect and send resolution type to testers as reply.
Test Closer After completion of all possible test cycles executions, test lead conducts a review with testing team to estimate completeness & correctness of testing.
Sign OFF After completion of test closer, test lead concentrates on final test summary report creation. It is a part of software release note. This final test summary report consists of below documents. ØTest Plan ØRequirements Traceability matrix ØAutomated Test Scripts if any ØTest Case and Defect Summary Report