Web www.softwaretestingsucks.com

Life Cycle Testing or V testing
In traditional waterfall model, testing comes at the fag end of the development process.No testing is done during requirements gathering phase, design phase and development phase. Defects identified during this disconnected testing phase are very costly to fix which is this model's biggest disadvantage.
Life cycle testing or V testing aims at catching the defects as early as possible and thus reduces the cost of fixing them.It achieves this by continuously testing the system during all phases of the development process rather than just limiting testing to the last phase.

The life cycle testing can be best accomplished by the formation of a separate test team.

when the project starts both the system development process and system test process begins. The team that is developing the system begins the systems development process and the team that is conducting the system test begins planning the system test process.Both teams start at the same point using the same information.The systems development team has the

and document the requirements for developmental purposes. The test team will likewise use those same requirements, but for the purpose of testing the system. At appropriate points during the developmental process, the test team will test the developmental process in an attempt to uncover defects.

The following is the software testing process which follows life cycle testing

Requirements Gathering phase:
Verify whether the requirements captured are true user needs
Verify that the requirements captured are complete, unambiguous, accurate and non conflicting with each other

Design phase:
Verify whether the design achieves the objectives of the requirements as well as the design being effective and efficient
Verification Techniques: Design walkthroughs, Design Inspections

Coding phase:
Verify that the design is correctly translated to code
Verify coding is as per company's standards and policies
Verification Techniques: Code walkthroughs, code Inspections
Validation Techniques: Unit testing and Integration techniques

System Testing phase:
Execute test cases
Log bugs and track them to closure

User Acceptance phase:
Users validate the applicability and usability of the software in performing their day to day operations.

Maintenance phase:
After the software is implemented, any changes to the software must be thoroughly tested and care should be taken not to introduce regression issues.
The life cycle testing is also called V testing. The project’s Do and Check procedures slowly converge from start to finish (see above figure), which indicates that as the Do team attempts to implement a solution, the Check team concurrently develops a process to minimize or eliminate the risk. If the two groups work closely together, the high level of risk at a project’s inception will decrease to an acceptable level by the project’s conclusion.
Home