system testing methodology

System Testing Methodology

QMITST01 / Version 1.0

Effective: June 15, 2005

Purpose

The purpose of system Testing methodology is

•

To define how system testing projects are executed and

•

To serve as a basis for different phases in a system testing project

Scope

During project planning, 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 system testing project which is taken up may go through all the phases of the Software
Testing Life Cycle which are detailed in this methodology, or may go through only certain
phases of Testing life cycle. For instance, a project may encompass only test execution 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 system 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 Exit (EITVOX) criteria defined for each phase.

Definitions & Acronyms

Definitions

Keyword

Definition

Bug Tracking

Bug Tracking process covers the defect lifecycle from identification of

a defect to its resolution / closure.

Functional Testing Process to determine that the features / functionality of the

application / product is as per the requirements

Load testing

Testing the application behavior under varying acceptable loads
Performance
Testing

Testing conducted to evaluate the compliance of a system or

component with specified performance requirements

Regression Testing

•

Process to ensure that the earlier applications/ products still

work with the new changes.

•

Tests ensure that changes do not introduce unintended

behavior or additional errors.

Smoke testing

Smoke testing to ensure the build version is ready for undertaking

testing

System Testing

Process to determine that the system functions as intended or

documented.

Acronyms

Acronym

Explanation

STC

System Test Cases

STP

System Test Plan

Overview

The system Testing process starts with analyzing/ Understanding of Business/ Functional
requirements.
System testing Objectives are identified specified and prioritized.
(Depending on the client requirements System test may include different tests like Functional
Test, Regression Test and Load-performance Test).
The System Test plan is created.
Test Cases are prepared to validate if requirements are met.
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.
Test Automation follows the manual Test Execution as per Customer Requirement
Defects identified during the system Testing are entered in to Defect tracking process.
Test Result Reports are generated after completion of Testing.

The System Testing project comprises of the following phases:

1. Analyze Requirements

2. Create System Test Plan
3. Create System Test Cases
4. Ensure System Testing Environment
5. Execute System Test Cases
6. Review System Test Results.
7. Prepare Test Report

References

QEdge Testing Methodology
Functional Testing Methodology
Regression Testing Methodology
Load-Performance 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)

Requirements Analysis

This phase consists of requirements from BRS/ SRS and Design documents to understand the

application functional areas and prioritizing test objectives

Entry

Requirements Specification and Design Specifications are available

Inputs

•

Requirements Specification (BRS/ SRS)

•

Design Specification

•

User Guide

•

Installation Guide

Tasks

•

Study and review the system Requirements document

•

Understand application/product architecture in Design

Specification document

•

Specify Test Objectives

•

Define Strategy/ Approach

•

Specify Acceptance Criteria and completion criteria for each test

objective.

•

Prioritize the Test Objectives as High and Medium

•

High - Most important tests: must be executed

•

Medium - Second-level objectives: should be executed after high-

priority tests

•

Identify scope of Automation.

•

Identify Test Automation Tools as required

Verification /

Validation

•

Review of Test Objectives

•

Review of Scope.

Outputs

•

Identification of critical areas

•

Prioritized test objectives

Exit

•

The test objectives are prioritized

•

Approval of Scope

Create System Test Plan

This phase consists of creation of System Test Plan after understanding the requirements. The
plan basically consists of Test Criteria, Scope, Environment, Estimations, Risks, Defect
Tracking, Build Management (Refer… Guidelines for Build and Release Management, Guidelines
for Metrics Definition Standard, Guidelines for Defect Management)