V module

Verification Validation
Development stage Testing Stage

Information Gathering Assessment of Dev. Plan

Analysis Preparation of Test Plan
Requirement of phase Testing

Design & Design Phase Testing

Coding Program Phase Testing
Test Case Design

(Installation Build) Sanity Testing

Integration Testing System & functional Testing
UAT
Test Documentation

Maintains DRE
RFC
Post marten testing
Regression Testing
 V module stands for V & V
 In V module V & V working parallel
 It is mapping between development stage & testing stages to validates Customer
requirements
 In V module suppose you have completed Development of one stage , and second
stage is running & if any change in requirement CR comes for first stage – we can go
back to first stage and fulfil that CR with extra amount
 V module generally preferred for big organization
 Duration 3 plus months
 How Decides V module process - Client
 Extra money – for change in requirement

Information Gathering
Analysis

1. Assessment of development plan –

Defining objective of project – Banking, Telecom, Health Level

Taking/Defining steps to how we can achieve objective of project

Assessment of development plan – making the strategy for Testing

This phase decides which methodology we are going to use in our testing

Assessment of development plan – making the strategy for development also get decided

they plan which methodology is used like Automation Testing, Manual Testing

Defined by CEO or Top Level persons of company

Test responsibility matrix is get finalized .TRM.

Example: BCCI – Format – IND vs AUS

Strategy depends on format Test|1 Day |T20

2. Preparation of test Plan –

Implementation of TRM is done in preparation of Test plan

Project manager is part of it & responsible for TRM Implementation

Project manager choose team

Team leader prepare Test Team

He distributed work to all team member

And ask for the estimation – estimation means how much time it will take to complete
test – start to end time

Job Allocation

Resource Allocation

Estimation

3. Requirement of phase testing

Phase means Unit

In this phase estimated requirements of phases are finalized

eg. One Application contains number of phases/ Modules

PayTM –

PayTM > Recharge – Travel – Flight – Train – Movie

Continually Introduces new modules like. Money Transfer – so we need requirement

estimation

In one projects different phases are there (say 100 phases) – That developer & tester has
to develop & Test
 Design & Coding

4. Design phase Testing

5. Program Phase Testing

Design & program phase testing means code testing

Code testing - start from small unit of program.

Developers are involved in both process

Developers known the internal coding & if any difficulty or error identified he is able to
solve this

This phase means like white box Testing – Unit Testing

6. Test Case Design

Design test Case

Positive Test Cases Negative Test Cases

Test Cases Have Two Parts –

1. Positive scenarios testing & 2. Negative scenarios testing

Preparing the scenarios for Testing & same scenarios will execute in later as part of
testing
Testers are involved in this
This testing should carried out like Black Box Testing (+ Ve & - Ve)
As per The SRS documents we are preparing Scenarios/ Test Cases

Eg. Two Step Authentication

SBI online Transfer Login Page

SRS - Page 1 – UN & PSW

SRS Page 2. Mobile Number (* Mandatory)

Positive scenarios?

Negative Scenarios?

7. Integration (Build Installation)

Under 3 month’s period in V module – 5 to 6 modules are developed

Sometimes in Current running project, organization got new requirements to develop as

a new module – which Clint / customer wanted to add in existing flow

It is nothing but integrating new module or Requirement in main module depending upon
HLD & LLD

Development Team will work on new requirement > Develop code for that > perform
WBT on that > and when module is ready they add/ Integrate module into existing or old
application Flow

Example – Amazon E-comers’

Home – Fashion – electronics – Mobile - flight - Beauty –

Existing Flow

Mobile – view Product – Buy Product/Add –place order – payment – delivery

 New

Mobile – view Product – Buy Product/Add –Exchange - place order – payment – delivery

Device Company

Module

Year

IMIE

Price

Developers are responsible for integration testing

White box tester performs integration testing

New sub module or phase designed, Developed and integrated in already existing flow by WBT

Integration Testing has two types

Front End integration – Front end developer combine all dependent module using CALL

function

Back End Integration - Back end developer combine all the table together using JOIN function
 8. Sanity Testing

Sanity testing comes under Validation process

Tester is involved & responsible for this process
In sanity Tester validates basic & core functionality of application
Tester test main flow of application
Checked application for blocker
Only critical defects or blockers defects are raised
Example – IRCTC
Plan my Journey > my booking > PNR Enquiry > Refund History
Source to Destination
Class
Date – Date Format

My booking – Reservation information, Date, Time, Class, Train Number

Number of station in between count is incorrect - it’s fine

PNR – Railway logo

Text Field to accept number
Submit button / Search Train – Not working – it’s critical one & raised – service not found
After Integration Testing first Sanity Testing comes in picture

9. Functional & System Testing

After sanity Testing Functional & system is carried out

BBT is involved & responsible for it

In this testing tester checks all the functionality of application start to end step by step to

ensure QA & QC

End To End Testing

Testing is carried out with Positive & negative scenarios as per the SRS documents

In this type of testing tester find out small defects as well as critical or large defects
Example: same IRCTC Above

Logo

PRN Number UI

Number of station Count

10. UAT – User acceptance Testing

Client/Customer involved in UAT | End to End functionality testing

After performing F & S system testing, we assure about Bug free application (Means
defect free application)
After F & S validation – Client and Tester are sited together and checks entire
functionality start to ends as per the requirement
UI, Main Modules, Sub modules, logo, colure etc. as per requirements
After removing defects, once F & S testing completed application or product moved to
UAT.

After validation of product in UAT – it goes to production

11. Test Documentation

Preparing & maintaining testing reports – is a part of testing

Tester is responsible for it
It includes
Test Summary Report
Defect Report
Daily Testing Report
Scenarios execution report daily/ Week/ monthly – PASS or FAIL
Eg. Worked on Recharge module – Prepaid & postpaid
Name Scenarios Executed Status Comments

Tester send this report to > Team Leader

Team Leader Send it to > Project Manager
Project manager send it to > ?

BA send it to > ?

Defect Removal Efficiency

There are 4 phases of testing environment

DIT – Development integration Testing – Developers

SIT – System integration Testing - Tester
UAT – User Acceptance Testing - DEV & Tester & User
Release or Production

DRE - It is process to calculating at which level Tester performed the testing

Calculating Efforts of Testing

DRE – calculates at which level tester tested application

- Calculates test efficiency

DRE has two phases –

A – Defect found By Tester
B- Defect found during UAT

During the testing some of the defect is solved & some of the defects are canceled
Why canceled? - Not a bug, duplicate etc

E.g. In SIT we found 100 defects

Out of 100 defects
90 defects are solved
10 defects are canceled
 So we only consider 90 defects

IN UAT – when client test the application and if he founds some defects that defects also
taken into consideration

Example – in UAT we found 10 defects

A = 90 Defects
B = 10 defects

Then DRE = A 90
= 0.9
A+B 90+10

DRE Remark
0.8 to 1 Good Testing
0.5 to 0.7 Avg Testing
Below 0.5 Below Average

RFC – Request for change

Once SRS is finalized & customer wants to add some new changes or additional requirement
during the production at the time of release it is considered as request for change or change in
Request CR

To handles CR – There is Configuration management Team

CR Teams includes – BA+ Developer +Tester
We have 4 Testing phases
DIT – SIT – UAT – Release
So, in which environment we did the changes is decided by configuration management Team
For every new change in requirement, we have to pay extra money for it
Change in requirement is mentioned in SRS documents at
the end It is mentioned in red color with * mark
SRS is PDF format

Post mortem Testing

It is used to check complex / critical functionality of

application.

In PMT - developers are involved.

When entire testing is done & when product is ready for production & if get any
difficulty or if product not reproducing desired output then developer check all module
in detail & performed WBT.
Finding out root cause of defect- exact where is & what is the problem

Ex. Online Store – Order- store-OCE- get order id- but order fails

Regression Testing

It is a subset of the sanity testing

As we know there are 4 stage environment

After completion of SIT & UAT testing, tester again check the basic and core functionality of
the system is called regression testing.
Dis-advange V-Module-

 In V-module deployment/ delivery time  3 month

 For every CR/ RFC, client paying some extra charge