Controlled copy

Framework
for
Testing

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected

Controlled copy Testing Framework

Table of Contents

1.0 Introduction............................................................................... .............................4

2.0 Definitions and Acronyms............................................................. ........................5

2.1 Acronyms...................................................................................................... .....................5
2.2 Definitions........................................................................................................ ..................5

3.0 Purpose...................................................................................................... .............6

What is not the intended use for the Framework?................................... ........................6
What then defines the process for the projects?....................................................... .......6
How should the Framework be used?................................................... ..........................6
4.0 Organization of the Framework.................................................................. ...........7
4.1 Section A – Process Disciplines.................................................................................. .....7
4.2 Section B – Standard PSPH ................................................................................ .............7

5.0 Section A - Process Disciplines................................................. ..........................9

5.1 Test Requirements Study ........................................................................................ .........9
5.1.1 Test Requirements Study (AWR)............................................................................ ......9
Scoping........................................................................................................................ ....9
Requirements Gathering ............................................................................................ .....9
Identification of Estimation Methodology............................................... ..........................9
Estimation ....................................................................................................... ............10
Business Process Understanding ................................................................... ..............10
Application Understanding.................................................................................. ...........10
Tools Understanding......................................................................................... .............10
Customer Testing Process Understanding........................................................... ..........11
Infrastructure requirements Understanding............................................................. .......11
Customer Performance Baseline Collection.................................................................. .11
Traceability matrix for Test Requirements........................................................... ...........12
Knowledge Transition to Offshore........................................................................ ..........12
5.2 Test Strategy.............................................................................................. .....................12
5.2.1 Test Strategy (AWR)........................................................................................... ........12
Tool Evaluation and Selection (in case of automated testing).................................... ....12
Testing Tools Installation (in case of automated testing).......................................... ......12
Proof Of Concept (in case of automated testing).............................................. .............13
Test Strategy formulation................................................................................ ...............13
5.2.2 Test Planning (AWR)............................................................................... ...................14
Test Planning................................................................................................. ................14
Receive requests from Customer......................................................... .........................14
Revisit Test Strategy ........................................................................................ .............15
5.3 Test Design................................................................................................................... ....15
5.3.1 Test Environment Setup (AWR)............................................................................ ......15
Test Environment Setup.............................................................................................. ...15
5.3.2 Test Design (AWR)........................................................................................ .............15
Test Design ......................................................................................................... ..........15
Test Data Preparation / Customization / Sampling / Manipulation.................................16

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 2 of 22

Controlled copy Testing Framework

5.4 Test Execution...................................................................................... ...........................17

5.4.1 Test Execution (AWR)...................................................................... ..........................17
Pilot Execution of Test cases......................................................................... ................17
Test Execution......................................................................................... ......................17
5.5 Delivery....................................................................................................................... ......18
5.5.1 Delivery (AWR)...................................................................................................... .....18
Delivery..................................................................................................................... .....18
Verification by Onsite team............................................................................. ...............18
5.6 Acceptance Testing................................................................................... ......................19
5.6.1 Acceptance Testing (AWR)............................................................................... ..........19
Acceptance Test Plan................................................................................. ...................19
Acceptance Test Procedure................................................................................. ..........19
Assist in UAT Data Preparation........................................................... ..........................19
Acceptance Testing....................................................................................................... .19
Acceptance Sign – Off................................................................................... ................20
6.0 Section B – Process Handbook (ETVX)......................................... ...................21

7.0 Section C – Measurements Applicable.......................................... .....................22

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 3 of 22

Controlled copy Testing Framework

1.0Introduction
This handbook describes the Cognizant Testing framework and applies to Projects
executed by Cognizant delivery team as part of

1. Standalone projects taken up for any new/existing customer.

2. ODC engagement with existing customers,
This framework is organized as follows:
− SECTION A – TESTING WORKFLOW
− SECTION B – STAGES OF TESTING
− ANNEXURES

Section A – Testing Workflow

The testing workflow refers to the logical group of tasks performed during the testing
process. Logical grouping aims at grouping tasks that fulfill a common objective like
System testing, Delivery etc.

A similar workflow exists for the Project Management process, which happens in
parallel / overlaps with the testing workflow. (Refer to the Delivery Management
Framework for more details)

Section B –Testing Process (ETVX Model/ OSSP)

Tasks in Testing workflow and Project Management workflow are fitted into the
different stages of Testing operational model

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 4 of 22

Controlled copy Testing Framework

2.0Definitions and Acronyms

2.1Acronyms
NFR Non functional requirement

RFP Request For Proposal

SOW Statement of work

AWR Activity, Work Product, Responsibility

ODC Offshore Development Center

POC Proof of Concept

2.2Definitions
ROLE The roles depicted here identify the skill background of the people
doing the tasks. A Project team member could be playing more than
one role. It is suggested that projects do a mapping of the roles to the
team members accordingly

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 5 of 22

Controlled copy Testing Framework

3.0Purpose
The primary purpose of this framework is to describe the testing related practices
that are applicable to projects executed by Cognizant.

Where special guidelines are available, they have been referenced in the
framework. It is recommended that such guidelines be read and understood entirely
to have a complete understanding of the Testing Framework.

The practices that are mandatory for all projects and the practices that are optional
for the projects are listed in separate boxes throughout the framework. An
explanation of the legends is provided below:

 Mandatory / Optional Discussions

Guidelines

 Notes

What is not the intended use for the Framework?

The Framework cannot be considered to be the PSPH for the project.
Understanding this is important, as the framework is not organized by Stages. It is
rather organized by process disciplines. The Section B of the Framework contains
references to PSPH, which defines the process to be adopted by the projects.

What then defines the process for the projects?

The Section B of the Framework contains references to PSPH, which defines the
process to be adopted by the projects.

How should the Framework be used?

1. The Framework provides the basis on which all Operational life-cycle
models are defined.

2. Additional operational life-cycle models needs to be arrived at using the

Framework as the basis.

3. The Framework splits each of the tasks in the PSPH into further activities
thus explaining how a task needs to be performed. Further references are
provided to Testing guidelines that describe the Inputs, Outputs, and Tools
& Techniques to be performed for each of these tasks.

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 6 of 22

Controlled copy Testing Framework

4.0Organization of the Framework

This framework is organized as follows:
− SECTION A – Standard Cognizant Process Disciplines
− SECTION B – Standard PSPH for QSM defined Operational Life-cycle
models
− SECTION C – Measurements Applicable. This provides a reference to the
DM Framework where Metrics Plan and Guidelines have been consolidated
across Solution Offerings

Framewor
k

Standard Standard
Cognizant Cognizant PSPH
Process

Tasks Stages

Activitie Tasks
s

4.1Section A – Process Disciplines

This refers to the logical groups of tasks performed during the testing process.
Tasks from a logical group could be split across several stages and the process
discipline provides an approach to view information from a logical view.

If the project wished to understand the total effort spent on Acceptance Testing (for
all the activities done as part of Acceptance Testing), it may not be possible only
using stages as the plan for Acceptance Testing is done upfront in the project.

During the start of the project, the tasks are mapped to the chronological stages in
the projects while the Process Discipline mapping is fixed, abstracted but available
for reporting purposes.

4.2Section B – Standard PSPH

Here the stages of Application development life cycle are depicted.

Tasks from the various Process Disciplines are fitted into the different stages

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 7 of 22

Controlled copy Testing Framework

depending on the life-cycle model chosen for the project

Advantage of distinguishing Process Disciplines And Stages

1. Tasks can be looked upon as components, which can be plugged and played
into different Stages of the project. The work products are tied to the tasks and
the entry criteria and exit criteria of the stages would vary depending on how the
tasks are interweaved.

2. Organizing tasks by process discipline and stages also helps in slicing and
dicing project metrics and help in comparing one versus the other.

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 8 of 22

Controlled copy Testing Framework

5.0Section A - Process Disciplines

5.1Test Requirements Study

5.1.1Test Requirements Study (AWR)

Scoping
Activity Work Products Responsibility
Define scope of testing (In Test Requirements Account Manager / Senior
Scope and Out of Scope) Document Business Analysts

Requirements Gathering
Activity Work products Responsibility
Requirement gathering Discussion notes / Business Analysts, Project
discussions and
CRAD Manager / Project Leader
clarifications
Study of system Business Analysts, Project
Requirements Test Requirements Manager / Project Leader
Documentation of software Document Business Analysts, Project
requirements and sign-off Manager / Project Leader

Identification of Estimation Methodology

Activity Work Products Responsibility
Evaluate Estimation Project Manager / Project
Estimation Sheet
methodologies Leader

Define Estimation Project Manager / Project

Estimation Sheet
methodology for testing Leader

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 9 of 22

Controlled copy Testing Framework

Estimation
Activity Work Products Responsibility
Estimation Sheet (If Test
Estimate for the total
Case Estimation: Test Case Project Leader
volume of work
Estimation Document)

Business Process Understanding

Activity Work products Responsibility
Understand and document the
Testing KT Document Project Leader
Application process

Understand and document

Technical aspects of the Testing KT Document Project Leader
application

Identify and define the

customer performance Customer Performance
Project Leader
baselines of the existing Baseline
system

Application Understanding
Activity Work products Responsibility
Understand the applications to
Testing KT document Project Leader
be tested

Understand and document the

interfaces to the application, if Testing KT document Project Leader
any
Understand the functionality
impacts on other external Testing KT document Project Leader
interfaces

Tools Understanding
Activity Work products Responsibility
Understand if there are any
tools used for testing in client’s Testing KT Document Project Leader
place

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 10 of 22

Controlled copy Testing Framework

Understand the test script

coding guidelines of the tool, if Testing KT Document Project Leader
any
Obtain Test Script Coding
Guidelines and User Manual if Testing KT Document Project Leader
any

Customer Testing Process Understanding

Activity Work products Responsibility
Understand and document the
Testing KT Document Project Leader
testing strategies used

Understand and document the

Testing KT Document Project Leader
testing techniques used

Understand and document the

various outputs of the testing
Testing KT Document Project Leader
process (like Test Results, Test
Cases etc.)

Understand the gaps in the

Testing KT Document Project Leader
existing Test Process

Infrastructure requirements Understanding

Activity Work products Responsibility
Understand and document the
hardware / software
Testing KT document Project Leader
environment that the
application is running

Identify if there are any

Testing KT document Project Leader
connectivity to be established

Customer Performance Baseline Collection

Activity Work products Responsibility
Identify if there are any
Customer Performance
Customer Performance Project Leader
Baseline
Baselines set

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 11 of 22

Controlled copy Testing Framework

Traceability matrix for Test Requirements

Activity Work products Responsibility
List down the test
Requirements Traceability
requirements to trace it Project Leader
matrix
throughout the testing life cycle

Knowledge Transition to Offshore

Activity Work Products Responsibility
KT of application systems,
existing test process,
- Project Leader
infrastructure setup etc. to
Offshore

5.2 Test Strategy

5.2.1Test Strategy (AWR)

Tool Evaluation and Selection (in case of automated testing)

Activity Work products Responsibility
Identify tools to be evaluated Test Tools Evaluation and Team Leads
Selection Report
Identify various evaluation Team Leads
parameters
Team members / Team Leads
Evaluate tools on the various
parameters Team members

Report findings
Review findings Test Tools Evaluation and Team Leads
Selection review report
Finalize tool to be used Test Tools Evaluation and Team Leads
Selection Report

Refer Black-Box testing questionnaire and Performance testing

questionnaire for evaluating various tools on Black-Box testing and
Performance testing

Testing Tools Installation (in case of automated testing)

Activity Work products Responsibility

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 12 of 22

Controlled copy Testing Framework

Installation, Setup and Tools ready to use Project Leader / Team Leads
customization of tools that
are finalized for testing

Proof Of Concept (in case of automated testing)

Activity Work products Responsibility
Proof of Concept in case of Proof Of Concept Document Team Leads
automated testing

Test Strategy formulation

Activity Work Product Responsibility
Determine the types of Test Strategy / Approach Project Leader / Team Leads
testing to be performed (Eg: Document
Unit / Integration / System
testing, Load Testing, Link
Testing, Performance Testing
etc.)
Define testing methodology
(Eg: Top-Down / Bottom-Up)
Define the risks involved and
assumptions made in the
project
Identify testing tools, if
applicable (This section can
be filled once the testing tool
is finalized)
Define the testing approach /
methodology to be followed
in case of automated testing

1. Refer Test Strategy Guidelines for various types of testing that could be
performed and various testing techniques

2. Refer Manual Testing Guidelines and Automated Testing Guidelines for

the difference in the testing process

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 13 of 22

Controlled copy Testing Framework

5.2.2Test Planning (AWR)

Test Planning
Activity Work products Responsibility
Types of Testing to be done Project Leader / Team
Test Strategy
are identified Leads

The tasks for Test Planning are Project Leader / Team

identified Leads

Test schedule is defined Project Leader / Team

Leads
Specific responsibilities are
assigned to team members Project Leader / Team
along with clear-cut deadlines Leads
Test Plan
Preparatory activities are Project Leader / Team
identified (Eg: acquiring Leads
special testing utility, hiring and
training engineers etc.) Project Leader / Team
Leads
Test items are identified

Project Leader / Team

Additional needs, if any, are
Leads
identified

Review Test Plan Test Plan review report Team Leads

Log Test Requests Team members

Test Request Sheet and
Identify the Deadlines (Start Tracking Sheet
Date and End Date) for the
Test Request

Update Requirements Updated Requirements

Team members
Traceability matrix Traceability matrix

Receive requests from Customer

Activity Work products Responsibility
Receive requests from Test Request and Tracking Team Leads / Team members
Customer Sheet

Requirements could come in two ways

1. Upfront Defined requirements

2. Adhoc requests which needs to be tracked

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 14 of 22

Controlled copy Testing Framework

Revisit Test Strategy

Activity Work products Responsibility
Identify if Test Planning has Updated Test Strategy Project Leader
brought in any changes to
the Test Strategy

5.3Test Design
5.3.1Test Environment Setup (AWR)

Test Environment Setup

Activity Work products Responsibility
Manual Testing

Setup System / Integration /

Updated Test Strategy
Unit Test environment as Team members
document
applicable

Setup System / Integration

Team Leads / Test DBA
databases

Run scripts and populate the Populated System / Team Leads

databases Integration database

Review System / Integration Test Environment review Team Leads

/ Unit test environment report

Automated Testing

Setting up the automated

Automated test bed Team Leads / Team members
testing environment

5.3.2Test Design (AWR)

Test Design
Activity Work products Responsibility
Manual Testing

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 15 of 22

Controlled copy Testing Framework

Identify the type of testing Team Leads/ Team members

Identify the scope of testing

Identify the pre-requisites for

testing

Identify the test scenarios for

generating the test cases
Test Procedure with test
cases
Generate test cases based Team Leads/ Team members
on the type and scope of
testing

Define execution and

verification procedures

Finalize environment data

requirements

Build test suites, test drivers as

Test Suites / Test Drivers Team members
needed for testing

Test Procedure review

Review Test Design Team Leads
report

Update Requirements
Updated Requirements
Traceability Matrix to include Team members
Traceability Matrix
test specifications

Automated Testing

Prepare Test Scripts Test Scripts / Test

Team Leads / Team members
Procedure

Review Test Scripts Reviewed Test Scripts Team Leads / Team members

Test Data Preparation / Customization / Sampling / Manipulation

Activity Work products Responsibility
Manual Testing

Prepare necessary test data

Test environment ready
for System / Integration / Unit Team members
with Test Data
Testing

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 16 of 22

Controlled copy Testing Framework

Test environment ready

Validate test data Team Leads
with validated Test Data

5.4Test Execution
5.4.1Test Execution (AWR)

Pilot Execution of Test cases

Activity Work products Responsibility
Manual Testing

Perform Pilot Run

Test Logs Team members
Log Results

Analyze Results Pilot Run Results Report Project Leader / Client

Define Corrective action, if

- Project Leader
necessary

Revisit Test Strategy, if Updated Test Strategy

Project Leader
necessary document

Test Execution
Activity Work products Responsibility
Identify the type of testing to be done -

Team members /
Identify number of test runs from the test plan. -
Team Leads
Test logs /As run
In every test run, Run test cases as per the test
logs (in case of
procedure and records results.
Automated Testing)
Record of disruption
If a test run fails altogether, because of an of Cycle completion
abortive functionality, then record the failure of in the test logs /As Team members
the run as a whole (E.g. RUN N: ABORT M) run logs (in case of
Automated Testing)

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 17 of 22

Controlled copy Testing Framework

Once the abortive failure is corrected, restart Test logs /As run
the Test Run and repeat for all the planned Test logs (in case of Team members
Runs Automated Testing)
Update Requirements Traceability Matrix to Updated Requirements
Team members
include test results Traceability Matrix

5.5Delivery
5.5.1Delivery (AWR)

Delivery
Activity Work products Responsibility
Zip / Pack the testing documents Zipped file containing Test Plans
Project Leader /
(typically Test Plans, Test Procedures / / Test Procedures / Test Logs for
Test Cases and Test Logs) for the Team Leads
the tested module
tested module / requirements
Project Leader /
Summary Report
Prepare summary report for testing Team Leads

Verification by Onsite team

Activity Work products Responsibility
Verification mail from Onsite co- Onsite Co-
Deliverables verification by Onsite
team ordinator ordinator

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 18 of 22

Controlled copy Testing Framework

5.6Acceptance Testing
5.6.1Acceptance Testing (AWR)

Acceptance Test Plan

Activity Work products Responsibility
Plan for Acceptance Testing Acceptance Test Plan Customer and Cognizant

Acceptance Test Procedure

Activity Work products Responsibility
Test Requirements
Determine Acceptance Criteria Customer and Cognizant
Document
Identify Acceptance test Customer and Cognizant
scenarios Acceptance Test
Procedure
Define Acceptance Test Cases Customer and Cognizant

Assist in UAT Data Preparation

Activity Work products Responsibility
Acceptance testing
Prepare Acceptance Test Data environment ready with Customer and Cognizant
test data

Acceptance Testing
Activity Work products Responsibility
Review and communicate
Updated Acceptance
any changes to the Client / Cognizant (S)
test plan
acceptance test plan

Get the acceptance test

Acceptance test cases Cognizant Delivery Manager
cases and review the same

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 19 of 22

Controlled copy Testing Framework

Support during acceptance Issue Resolution, Test Onsite coordinator / Delivery

testing logs from the client manager

Acceptance Sign – Off

Activity Work products Responsibility

Get Acceptance sign-off from

Formal mail from Client Customer
customer

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 20 of 22

Controlled copy Testing Framework

6.0 Section B – Process Handbook (ETVX)

Testing Project Software Process HandBook

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 21 of 22

Controlled copy Testing Framework

7.0Section C – Measurements Applicable

Metrics Plan for Testing

Release ID: QFTS-FW.doc / 1.01 / 05.03.2004 C3: Protected Page 22 of 22