4. Testing: Creation and Execution
In this step a testing team is finally at the stage where they need to put all their prep work to use. A testing team must use their templates and timelines to first prepare all test cases and plans. This should include a review of the test plans for completeness and authenticity. Ensure each test case has, at least a serial number, description, priority, relevant test data and the expected outcome or result. Negative test cases should be marked appropriately. One important consideration to take into account is, if the application will be automated, the team should mark each test case that is considered important and relevant enough to automate. Final plans should be signed off by concerned Dev Managers, Business Analysts and the Team Lead. Some organizations even ask end users to review the test plans and "informally" sign off on them.
Once completed, a testing team will be all set to begin. Refer to the WBS in step 2, use the test plans and execute them within the timelines stated. Delays coming early in the testing project should be appropriately communicated to the team lead over an informal conversation or a formalized report, varying in frequency from company to company. The team lead in turn should communicate to other key players in the project ensuring that testing functions as one integrated unit of the SDLC.
Also, do not forget to create the appropriate metrics along side the testing. Before one knows it, people will start asking for them and will start determining the "health" of the release based on the QA reports.
5. Loop
Several successful test cycles later, the testing manager and team will have managed to sign off on the software and ultimately facilitating successful deployment. Does this mean the mission is complete? Absolutely not! If the software was a success, there will always be additional work including new releases and new deadlines. At this point, the team has definitely come a long way given that all necessary testing related processes have been set in place. However, this will be the true test of expansibility. This is a test of how efficient and comprehensive the test strategy, testing templates and protocols are. The key point to note here is that incorporating flexibility and adaptability in your initial approach goes a long way to ensure that the testing team has minimum rework with every new deployment.
