Testing Process

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential

Objectives
 At the end of this session, you will be able to:
 Understand the Testing process
 Get familiarize with different Testing Roles.
 Get an overview of Testing Environment.
 Understand Test Data
 Get an overview of Traceability Matrix

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 2

Testing Process
 Software testing is performed by an independent group of
testers after the functionality is developed before it is
shipped to the customer.

 The objective of testing process should be to reduce risks

inherent in a software being developed.

 Software testing can be started at the same moment the

project starts.

 Agile software development movement is a test-driven

software development model that is used widely today.

 In this methodology unit tests are written first, by the

software engineers (often with paired programming in the
extreme programming methodology).

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 3

Testing Process Contd..
 Testing is carried out Manually with major or minor
automation as per the necessity and circumstances

 What is Manual Testing?

 Testing performed by a human, without using any third party
tools

 What is Automation Testing?

 Testing performed using a third party tool is called as
Automation Testing

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 4

Testing during each phase of SDLC
 Requirement phase testing
 Verification of requirements definition
 Determine test strategy
 Determine adequacy of requirements
 Generate functional test conditions

 Design phase testing

 Determine consistency of design with requirements
 Determine adequacy of design
 Generate structural and functional test conditions

 Coding phase
 Determine consistency with design
 Determine adequacy of Implementation
 Generate structural and functional test conditions for units

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 5

Testing during each phase of SDLC
 Testing phase
 Establish test objectives
 Design test cases, Write test cases
 Review test cases, Execute test cases
 Examine test results

 Installation phase
 Version control (correct version and complete build of system is
installed)

 Maintenance phase
 Modify and retest
 Regression testing
 Document updation

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 6

Testing Roles
 Following roles are more or less standard on most testing
projects:
 Tester
 Test Engineer
 Test /QA team lead
 Test /QA Manager
 System Administrator
 Database Administrator
 Technical Analyst
 Test Build Manager
 Test Configuration Manager

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 7

 Test Environment

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential

Test Environments
A partition of hard drive which contains the source code,
binary code and test data is called a ‘test environment’

 Objective: To be able to test at the desired level with

appropriate data

 A test environment consists of a

 Test lab or labs and includes test plans that detail what you will
test and

 Test cases that describe how you will test each component.

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 9

Test Environments (contd…)

Environment Used for Owner

Development making changes in code Development team
followed by unit testing;
Sometimes used for
integration testing
System Test system testing Testing team or an
independent test
group
Acceptance Test acceptance testing Customer
Production This is where lies the ‘live’ Customer
(real) data and ‘in-use’
executables (binary code)

 Code is migrated from one environment to the next

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 10

Test Data
 Test data conceptually means creating representative
processing conditions using test transactions

 Test data : data which have been specifically identified for

use in executing test scripts, and are used to verify the
expected results obtained

 Test data which is specifically identified for use in executing

test scripts, and are used to verify the expected results
obtained

 Test data is generally created by the testing team.

Sometimes an extract of live data may be added.

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 11

Test Plan
 A test plan is a systematic approach to testing a system such
as a machine or software. The plan typically contains a
detailed understanding of what the eventual workflow will be.

 Test plans in software development

 In software testing, a test plan gives detailed testing
information regarding an upcoming testing effort, including
 Scope of testing
 Schedule
 Test Deliverables
 Release Criteria
 Risks and Contingencies

 It is the essential skill of a tester to construct a good Test

Plan; for which a formal training & experience as well
becomes significant aspects.

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 12

Traceability Matrix
 Software is constructed through various life cycle stages
such as requirements analysis, design, coding and testing

 Once the requirements are determined, it is important to

‘tie-up’ the elements of subsequent life cycle stages to all
these requirements

 It is precisely for this purpose that a ‘traceability matrix’ is

prepared and maintained

 Its columns correspond to lifecycle stages – requirements,

design, program specifications and test cases

 Check ITS-E-T026 template embedded

Microsoft Office
Excel Worksheet

CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 13

 Thank You

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential