Testing Levels in V-Model

Testing levels in V-model

1.   Unit testing

2.   Integration testing

3.   System testing

4.   User acceptance testing

Static Testing and Dynamic Testing:

1.   Static Testing:

Without executing a program/application finding mistakes is called Static testing

2.   Dynamic Testing:

While executing a program/application finding mistakes is called dynamic testing

Ex:

Check availability of components in Login window à static testing

Check click on “Cancel” button will close login windowàDynamic testing

 Check controls spelling correct or notà static testing

Check clarity of image objects à static testing

**Verification and Validation

Verification:

·       In this process to check “Are we developing the product right or not”?

·       Reviewing the SRS\FRS Document, Design Document, and Code to find any mistakes performs it.

·       **It is considered as “Static” testing i.e. inspection without the execution of computer

·       Peer Review, Walkthrough and Inspection are the examples of Verification Techniques.

a. Peer Review: It is an informal meeting where the author provides the document to any one person to identify any mistakes.(review between same level people/colleagues)

b. Walkthrough:

Semi-informal meeting where the participants come to the meeting and author gives the presentation.

In this case author himself is the presenter for explaining the project requirement.

It is planned meeting characterized by team of 2-3 people, led by author

Objective is to make other participants to get knowledge on requirements and to find any mistakes

c. Inspection:

It is a Formal meeting with 5-6 members

The meeting is led by the Moderator

Presenter is the reader other than the author

Recorder/Scribe records the defects identified in the meeting

Objective is to find any defects and communicate any important work product information.

**Explain advantages of reviews?

·       We can identify mistakes at early stages

·       We can develop quality product

·       We can have good knowledge on the functionality of the application

·       We can get confident on us

Validation:

·       In this process we check “Are we developed right product or not"?

·       It is the process of confirmation whether software meets customer requirements.

·       It is performed by executing the application to find any defect

·       **It is consider as “DYNAMIC” testing or testing with execution of computer

·       Unit testing, Integration testing, system testing and Acceptance testing are the examples of validation techniques.

Note: verification is required for validation activities also. i.e. reviews required for all testing phases

Verification is implemented by developers, testers, and quality assurance team members depending on the project activity.

Validation is implemented by testers