A testing life cycle is a part of Nimap Infotech software development life cycle in order to avoid major defects and complications with the end product. The testing life cycle is the various activities and stages of testing that a software product goes through before it is released. We at Nimap Infotech under the guidance and Leadership of Sagar Nagda, The Industry GURU in software testing, have designed the stages of the testing life cycle are often similar to those of the software development life cycle (SDLC)
In the first stage of the testing life cycle developers and testers usually analyze the requirements used in designing the product. Testers are especially useful in this stage because they tend to see things more from the users point of view.
Once the requirements of the project are examined, a test plan is created and documented. In this stage the software test plan (STP) document is written. The STP provides the scope of testing, testing approach, required resources, schedule, etc.
Once the test plan is complete, the next stage in the testing life cycle is test analysis. In this stage, our team develops test scenarios. We prepare test cases based on boundary conditions as well as positive, negative, and real world scenarios. Some important outcomes of this analysis it to make sure that all requirements are covered by at least one test case.
In this stage of the testing life cycle, the test is designed based on the requirements documented in the SRS. Sometimes, an end-to-end checklist that covers all of the features of the project is created. The various software modules and the paths connecting them are identified as well. Decisions on manual vs. automated testing are finalized. The team also sets the standards for unit testing and the pass/fail criteria, finalizes the testing schedule, and prepares the testing environment.
In this stage, the planned test cases area executed. Functionality testing is done. Top level testing is usually performed to locate failures and bugs, which are reported to the development team so they can provide any possible workarounds.
The results of testing are analyzed. If a bug is found and fixed by the development team, the test case is rerun. After a successful execution of the test case we decide if it passes or fails.
Keeping track of bugs is very important in a testing life cycle. It is a good idea for a project team to follow a specific bug life cycle. One document that is sometimes created during this stage is the Defect Profile Document (DPD). This document keeps developers informed about defects and may assist in the prevention of future bugs. It usually contains the following information:
â€¢ Unique identifier for the defect
â€¢ Test case where the defect occurred
â€¢ Date when defect was found and reported
â€¢ Detailed description of the defect
â€¢ Name of person that found the bug
â€¢ Version of the software in which the bug was found (and fixed if applicable)
â€¢ Name of the person that the defect was assigned to
â€¢ Severity of defect
â€¢ Priority of defect
â€¢ Current Status
Reporting and Rework
Testing is an iterative process. This means that once a bug is reported and fixed, it goes through the testing process again to assure that an adequate resolution was found. Regression testing is often included as a part of this stage.
Final Testing and Implementation
This stage of the testing life cycle usually focuses on the remaining levels of testing. This may include acceptance, stress, load, performance, and recovery testing. Even after the quality team determines that the product is ready and that the software can be released for production