Software Testing Models

                                                     Software Testing Models

1) Software Testing Life Cycle STLC: 

Software testing has its own life cycle that intersects with every stage of the SDLC. It also explains which testing activity needs to be carried out and when. Different phases of the software testing life cycle have been explained with the help of below diagram.

Requirement Stage:

During this phase Testing team studies client and system requirement to understand  what exactly customer required.

Understand requirement like functional non function. 

Formal meetings of the team can be held in order to document the requirements which can further be used as software requirements specification or SRS.

Test Plan:

After Understanding & Analyzing Product Requirement team move towards Planning . 

During the planning stage, the team of senior level persons comes out with an outline of Testing Plan at High Level.

Like scope of testing , Approach of testing , Time ,Risk,waht should be tested and not to be tested

Test Design:

Test design is done based on the requirements of the project documented in the SRS. This phase decides whether manual or automated testing is to be done. In Manual we have to write test case by considering different scenario & In automation testing, different paths for testing are to be identified first and writing of scripts has to be done if required. An end-to-end checklist that covers all the features of the project is necessary in the test design process.

Testing Execution:

In test execution what ever test case or test script is prepared already in test design we start executing those test case/script and if any bug or defect found we have to report to project lead or project manager.

Test Report & Clouser:

Test Closure Doc is the note prepared before u formally completes the testing process.

The test closure doc is nothing but the test summary report which we give after the whole testing is finished.

Numbers of test cases executed, no. of defects found,Defect density, Slippage ratio, consolidated test result report

===============================================================================

2) Agile Model:

Here release as frequently as every week rather than month and continuous changes in requirement and welcome to be integrated

============================================================================================

3) V-Model:

 

It is extension of water fall model .here both the aspect of quality is covered i.e 

quality control and quality assurance are covered. This model indicates that testing exits in every phase of SDLC life cycle

 

  The Left hand Side indicate software development life cycle and right hand side indicate software testing life cycle .development team follows "Do-Procedure " to  achieve the goal and testing team follows "Check Procedure" To achieve the goal

                 V Model is a process where development & testing can do parallel. For every development phase there is a testing phase. Development phases are called as verifications & testing phases are called as validations. Here the verification means the software implements correctly or not & the validation means the software that has been built is traceable to customer requirements or not.