To better understand Testing Life Cycle here we will touch upon following topics:
• Need of Testing Life Cycle
• Different Phases of Testing Life Cycle
• Where It fits in Software Development Life Cycle (SDLC)
Need of Testing Life Cycle
There are multiple testing activities that needs to be performed throughout the SDLC and these activities need to organize in a way that it ensures that the quality goals of the software are achieved. Organisations of all the testing tasks ensures better results in replicating these activities in other projects also. As this life cycle is specific to Testing process so all the software testing aspects are given adequate consideration to improve the overall quality of software and in turn increase the customer satisfaction.
Different Phases of Testing Life Cycle
• Requirement Analysis: In this phase business requirement are captured and from that test requirements will be deduced. These test requirements will become the input for rest of the phases.
• Test Estimation & Planning: Based on the test requirements, testing scope, test strategy & estimation of testing efforts is done. All this information will be compiled in document which is called Test Plan. From now on test plan will be go-to document for all the software tester and test manager for all phases to come.
• Test Preparation: Test Requirements will be further broken down into Test Scenarios and then Test cases. While preparing test cases all positive and negative scenarios would be considered. Each test requirement will be mapped to one or more than one test case. This mapping will help in maintaining requirement traceability. Test cases requires test data for the execution so test data is also prepared in this phase. Different test cases will be prepared for all type of testing like Integration, System etc.
• Test Execution: Once the test cases are ready and the software is available for testing, these test cases will be executed on the software application for testing. Test case execution result will tell us how the software application prepared is faring again the requirements earlier laid down. For each test case failed there will be defect logged and the application code needs to be changed to resolve that defect. This updated code will again be tested to make sure that it is now in accordance with the requirements and application is now fully serving the purpose for which it is designed. Before making any application live, it is ensured that that delivered application is relatively bug free. To keep all the stakeholders updated with the status, test reports and dashboards are also prepared and shared with them on daily/weekly basis.
• Test Closure: This phase will be comprised of closing all the testing activities. Test matrices will be prepared to understand how actuals fare against what was planned. This will lead to pinpoint the areas which would need more attention in next cycle of testing. Lesson learnt will be captured which will be referred while planning for next cycle. Test cases will be controlled and assessed for automation. All the repetitive test cases will be converted to automated tests. This automated testcase pack will be used for testing when client report any operational defects.
Where it fits in SDLC
STLC goes hand in hand with SDLC. Both start from Requirement gathering and analysis phase and then branch out separately. Refer the image below for detail. Both lifecycles focus on 2 most integral part of software development. With the synergy of these lifecycle, it is ensured that the final product is up to the client expectations.
With
this we conclude this topic, if you have any further questions regarding
lifecycles you can post your comments.
No comments:
Post a Comment