Professional Documents
Culture Documents
000
End to End Testing Methodology
QMITEE01 / Version 1.0 Effective: June 15, 2005
Purpose
The purpose of End to End Testing methodology is
- To define how End to End Testing projects are executed and
- To serve as a basis for different phases in an End to End Testing
project.
Scope
During project testing, this methodology shall be used to define the
activities and work products for each phase.
Only the Testing specific activities are detailed in this methodology. For all
other activities like project management, configuration management, etc.
the project shall follow the processes defined as part of Qualify.
Each End to End Testing project which is taken up may go through all the
phases of the Testing Life Cycle. For instance, a project may encompass
only System testing phases based on the customer’s requirements. The
phases that will be followed during the course of the project will have to
be detailed in the Software Project Plan (SPP)-Testing of the project. The
applicable phases of execution, the associated work products, verification
and validation criteria for each of the relevant phases shall be at par with
this methodology.
The End to End Testing methodology offers the flexibility of entry and exit
through any of the defined phases. The user can use this flexibility by
following the Entry, Input, Task, Validation, Output and Exit (EITVOX)
criteria defined for each phase.
Keyword Definition
Bug Tracking Bug Tracking process covers the defect lifecycle from
identification of a defect to its resolution / closure.
End to End Involvement from the Design Phase to the Production
Testing Phase.
I.e. working in parallel with the development teams to
ensure that quality is assured at each phase. The model
followed is the ‘V’ model. This thus includes the various
levels of testing, namely integration testing, system
testing and acceptance testing.
Functional Process to determine that the features / functionality
Testing of the application / product is as per the requirements
Load Testing Testing the application behavior under varying
acceptable loads
Performance Testing conducted to evaluate the compliance of a
Testing system or component with specified performance
requirements
Regression • Process to ensure that the earlier applications/
Testing products still work with the new changes.
• Tests ensure that changes do not introduce
unintended behavior or additional errors.
Smoke Smoke testing is to ensure that the build version is
Testing ready to undertake for testing
Acronyms
Acronym Explanation
FTS Functional & Technical Specification
ITP Integration Test Plan
ITR Integration Test Report
STP System Test Plan
STR System Test Report
Overview
The End to End Testing process will cover Integration Testing, System
Testing and User Acceptance Testing.
Integration Testing
The Integration Testing process starts with analyzing/ Understanding of
High level Design documents.
The Integration Test plan is created.
Test Cases are prepared based on the system requirements.
Integration testing Environment is identified and setup is done to proceed
with Test Execution.
Tests are executed to ensure that the application meets the requirements.
Defects identified during the Integration Testing are entered in to Defect
tracking process.
System Testing
The System Testing process starts (when Integration Testing is completed
with analyzing/ Understanding of System Design documents.
The System Test plan is created.
Test Cases are prepared based on the system requirements.
System testing Environment is identified and setup is done to proceed with
Test Execution.
Tests are executed to ensure that the application meets the system
requirements.
Defects identified during the System Testing are entered in to Defect
tracking process.
Test result reports are generated after completion of testing.
References
• QEdge Testing Methodology
• Functional Testing Methodology
• System Testing Methodology
Tailoring Guidelines
It is recommended that this methodology be followed during the course of
the project. If any tailoring is to be made due to the customer’s
requirements, then the tailoring shall be documented along with
justification in the Project Tailoring Record (PTR). (Ref… Tailoring
Guidelines)
Integration Testing
Analyze Integration Requirements
This phase consists of analyzing requirements from High level Design
Documents and requirement documents, and arriving at the prioritized test
objectives
System Testing
Analyze System Requirements
This phase consists of analyzing requirements from High level Design
Documents and requirement documents, and arriving at the prioritized test
objectives