Test Life Cycle explained


The software development life cycle starts with the Requirement stage in which the tester gathers the maximum information from the company so as to ascertain what’s needed. The comes the test plan in which the tester plans how to go about the project which may include the features, approaches, methods, time, resources and tools needed for the project. Once the tester is done with the requirements and plan, then comes the design stage which is entirely based on the requirements of the client.

A checklist should be devised which checks regularly if the process is going smooth and we are getting the desired result. After this the design is drawn and as it is the most important part of the process so extreme care should be taken in this regard as it assesses the quality of the process. Once the tester is done with the design reviews he should then conduct the code reviews in case there is a bug in the code that might pop up later so as to mitigate the future risk that may arise.

Various test cases are prepared based on the various options as to what a user may face during the life of the project and on the basis of which the test is executed and the reports are generated on the basis of the results of these tests. All the bugs that pops up during the tests are reported and ensured that they do not disrupt the project during the actual working. Once the bugs are fixed, the project is given to the quality assurance department which conducts another test to ensure there is no hindrance in the project execution and finally the project is released at the end of the life cycle.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>