Unit – III: Test Management
3.1 Test Life Cycle
Definition
Test Life Cycle (TLC) or Software Testing Life Cycle (STLC) is a systematic process followed
by the testing team to perform testing activities in different phases to ensure software quality.
Explanation
The Test Life Cycle defines the sequence of activities performed during the software testing
process. Each phase has specific objectives and deliverables.
The main goal of the test life cycle is to ensure that the software is tested in a structured and
organized manner, which improves software quality and reduces defects.
The testing team performs several activities such as:
• Understanding requirements
• Planning the testing process
• Designing test cases
• Executing tests
• Reporting defects
• Preparing test reports
Each phase of the test life cycle helps in identifying and correcting defects before the software
is released to users.
Phases of Test Life Cycle
1. Requirement Analysis
In this phase, testers study the Software Requirement Specification (SRS) document to
understand the system requirements.
Testers identify:
• Testable requirements
• Scope of testing
• Possible risks
The testing team also prepares the Requirement Traceability Matrix (RTM) to ensure all
requirements are covered in testing.
Real-Time Example
For an online banking system, testers analyze requirements such as login authentication,
balance inquiry, and fund transfer.
2. Test Planning
In this phase, the testing team prepares a Test Plan that defines the testing strategy and
resources required.
The test plan includes:
• Testing objectives
• Testing methods
• Required tools
• Schedule and timeline
• Roles and responsibilities
Test planning ensures that the testing process is well organized and efficient.
Real-Time Example
For testing an e-commerce website, the test plan defines how modules such as product search,
payment processing, and order tracking will be tested.
3. Test Case Design
In this phase, testers create test cases and test scenarios based on the system requirements.
Test cases include:
• Test case ID
• Input data
• Test steps
• Expected results
Test data required for testing is also prepared in this phase.
Real-Time Example
For a login system, test cases may include:
• Login with valid username and password
• Login with invalid password
• Login with empty fields
4. Test Environment Setup
In this phase, the necessary hardware, software, network configuration, and databases required
for testing are prepared.
The environment should be similar to the real production environment.
Real-Time Example
Setting up servers, databases, and application software required for testing a hospital
management system.
5. Test Execution
During this phase, testers execute the test cases and compare the actual results with expected
results.
If any mismatch occurs, it is recorded as a defect or bug and reported to developers.
Real-Time Example
Testing whether the payment module of an online shopping system processes transactions
correctly.
6. Test Closure
In the final phase, the testing team evaluates the testing process and prepares a test summary
report.
This phase includes:
• Reviewing test results
• Documenting defects found and fixed
• Analysing test coverage
• Preparing final testing reports
Real-Time Example
After completing testing of a college admission system, the testing team prepares a final report
summarizing the number of test cases executed and defects found.
Advantages of Test Life Cycle
• Provides a structured approach to testing
• Improves software quality
• Helps detect defects early
• Ensures complete requirement coverage
• Improves communication between developers and testers
3.2 Test Planning
Definition
Test Planning is the process of defining the testing strategy, objectives, resources, schedule,
and activities required to perform software testing effectively.
Explanation
Test planning is one of the most important phases in Test Management. In this phase, the
testing team prepares a detailed Test Plan document that describes how testing will be
performed.
The test plan provides a clear roadmap for the testing process, including what will be tested,
how it will be tested, who will perform the testing, and what resources are required.
Effective test planning helps ensure that testing activities are organized, efficient, and
completed within the specified time.
Preparing a Test Plan
Explanation
A Test Plan is a document that defines the scope, objectives, strategy, schedule, and resources
required for testing.
It provides guidance to the testing team about how the testing process will be carried out.
A test plan usually includes:
• Testing objectives
• Scope of testing
• Testing strategy
• Testing schedule
• Resources and tools required
• Roles and responsibilities
Real-Time Example
For testing an online banking application, the test plan may specify testing of modules such
as:
• Login system
• Account balance
• Fund transfer
• Transaction history
Deciding the Test Approach
Test approach refers to the overall strategy used to perform testing.
It defines the testing methods, techniques, and tools that will be used during the testing process.
Examples of test approaches include:
• Manual testing
• Automated testing
• Black box testing
• White box testing
Real-Time Example
In an e-commerce application, the testing team may decide to use:
• Black box testing for functional testing
• Automation tools for regression testing
Setting Up Criteria for Testing
Testing criteria define the conditions that must be satisfied before starting and completing
testing.
These criteria include:
• Entry Criteria – Conditions required to start testing.
• Exit Criteria – Conditions required to stop testing.
Real-Time Example
Testing begins only after:
• Software build is available
• Test environment is ready
• Test cases are prepared
Testing ends when:
• All test cases are executed
• Major defects are fixed
Identifying Responsibilities
In test planning, responsibilities of each team member are clearly defined.
This ensures that every task is assigned to a specific person and avoids confusion.
Responsibilities may include:
• Test manager
• Test engineer
• Automation engineer
• Quality assurance team
Real-Time Example
In a software company, the test manager assigns:
• Test case design to testers
• Automation scripting to automation engineers
• Test reporting to QA lead
Staffing
Staffing refers to selecting and assigning the required number of testers and team members
for the testing process.
Proper staffing ensures that testing activities are completed efficiently.
Factors considered during staffing:
• Project complexity
• Number of modules
• Testing schedule
Real-Time Example
A large banking software project may require multiple testers to test different modules such
as login, payments, and security.
Resource Requirements
Resource requirements include the hardware, software, tools, and testing environments
required to perform testing.
Resources may include:
• Testing tools
• Computers and servers
• Databases
• Network infrastructure
Real-Time Example
Testing a web application may require:
• Web servers
• Database servers
• Browser testing tools
Test Deliverables
Definition
Test Deliverables are the documents and reports produced during the testing process.
Explanation
Test deliverables provide evidence of testing activities and results.
Common test deliverables include:
• Test Plan
• Test Cases
• Test Scripts
• Defect Reports
• Test Summary Report
Real-Time Example
After testing an online shopping system, the testing team submits a test summary report
showing the number of defects detected and fixed.
Testing Tasks
Testing tasks refer to the different activities performed during the testing process.
Common testing tasks include:
• Requirement analysis
• Test case design
• Test environment setup
• Test execution
• Defect reporting
• Test reporting
Real-Time Example
In testing a mobile application, testers perform tasks such as executing test cases, identifying
bugs, and reporting them to developers.
3.3 Test Management
Test Management involves planning, organizing, controlling, and monitoring the testing
activities to ensure that software testing is carried out effectively and efficiently.
Two important aspects of test management are Test Infrastructure Management and Test
People Management.
Test Infrastructure Management
Definition
Test Infrastructure Management is the process of managing the hardware, software, tools, and
environment required to perform software testing.
Explanation
Testing infrastructure includes all the resources needed to conduct testing activities effectively.
Proper management of infrastructure ensures that testers can perform testing smoothly without
technical problems.
The testing environment should closely resemble the actual production environment so that
testing results are accurate and reliable.
Test infrastructure management includes:
• Setting up testing environments
• Managing hardware and software resources
• Installing testing tools
• Configuring databases and servers
• Maintaining network connectivity
Effective infrastructure management helps reduce testing delays and ensures efficient testing
operations.
Real-Time Example
While testing an online banking system, the testing team needs:
• Application server
• Database server
• Network setup
• Testing tools
These components together form the test infrastructure required for testing the banking
application.
Test People Management
Definition
Test People Management is the process of managing the testing team, assigning roles and
responsibilities, and ensuring effective collaboration among team members.
Explanation
In software testing projects, a team of testers works together to perform different testing tasks.
Test people management ensures that the right people with the right skills are assigned to
appropriate tasks.
It involves managing the testing team, monitoring their performance, and ensuring effective
communication between team members.
Key activities in test people management include:
• Assigning roles and responsibilities
• Providing training and guidance
• Monitoring team performance
• Encouraging teamwork and communication
• Managing workload and deadlines
Proper people management improves team productivity, efficiency, and quality of testing.
Real-Time Example
In a software company, the testing team may include:
• Test Manager – Responsible for overall testing strategy and planning.
• Test Lead – Supervises testing activities and team members.
• Test Engineers – Design and execute test cases.
• Automation Testers – Develop automated testing scripts.
Effective management ensures that all team members work together to achieve the testing
objectives.
3.4 Test Process
The Test Process refers to the structured activities performed during software testing to ensure
that testing is conducted in a systematic and controlled manner.
Two important activities in the test process are Baselining a Test Plan and Test Case
Specification.
Baselining a Test Plan
Definition
Baselining a Test Plan is the process of formally reviewing, approving, and freezing the test
plan so that it becomes the official reference document for testing activities.
Explanation
A baseline means establishing a fixed version of a document that can be used as a reference
throughout the project.
When a test plan is baselined:
• It is reviewed by stakeholders such as project managers, developers, and testers.
• Necessary corrections or improvements are made.
• The final version is approved and documented.
Once the test plan is baselined, it becomes the standard guideline for all testing activities.
Any changes to the test plan must go through a formal change management process.
Baselining helps maintain consistency, control, and clarity in testing activities.
Real-Time Example
In a banking software project, the test manager prepares a test plan describing testing
objectives, scope, resources, and schedule.
After review by project stakeholders, the document is approved and baselined, and the testing
team follows this approved test plan during the testing process.
Test Case Specification
Definition
Test Case Specification is a detailed document that describes the conditions, inputs, actions,
and expected results used to test a particular functionality of the software.
Explanation
Test case specification provides detailed instructions for testers to verify whether the software
behaves as expected.
It ensures that testing is consistent, repeatable, and well-documented.
A test case specification typically includes:
• Test Case ID
• Test Description
• Preconditions
• Test Steps
• Input Data
• Expected Result
• Actual Result
• Test Status (Pass/Fail)
Well-designed test case specifications help ensure that all system requirements are properly
tested.
Real-Time Example
Example: Testing a Login Function
Test Case
Test Steps Input Data Expected Result
ID
Enter valid username and
TC01 user123 / pass123 Login successful
password
user123 /
TC02 Enter invalid password Error message displayed
wrongpass
Warning message
TC03 Leave fields empty —
displayed
These test cases help verify whether the login functionality works correctly.
Importance of Test Case Specification
• Ensures systematic testing
• Improves test coverage
• Makes testing repeatable
• Helps track defects easily
• Provides documentation for future testing
3.5 Test Reporting
Test Reporting is the process of documenting and communicating the results of software testing
activities to stakeholders such as developers, project managers, and clients.
It helps track testing progress, identify defects, and evaluate the overall quality of the software
system.
Two important activities in test reporting are Executing Test Cases and Preparing Test
Summary Report.
Executing Test Cases
Definition
Executing Test Cases is the process of running the designed test cases on the software system
to verify whether the system behaves as expected.
Explanation
During test execution, testers follow the predefined test cases and perform the testing steps on
the software application.
The actual results obtained from the system are compared with the expected results defined
in the test case.
Possible outcomes of test execution:
• Pass – The actual result matches the expected result.
• Fail – The actual result does not match the expected result.
If a test case fails, the issue is recorded as a defect or bug and reported to developers for
correction.
Test execution also involves:
• Recording test results
• Reporting defects
• Re-testing after bug fixes
Real-Time Example
Example: Testing Login Function
Test Case ID Input Expected Result Actual Result Status
TC01 Valid username & password Login successful Login successful Pass
TC02 Invalid password Error message Login successful Fail
In the second test case, the system allowed login with an incorrect password, which indicates
a software defect.
Preparing Test Summary Report
Definition
A Test Summary Report is a document that summarizes the overall testing activities, results,
and defects found during the testing process.
Explanation
After completing the testing process, the testing team prepares a Test Summary Report to
provide a clear overview of the testing results.
This report helps project stakeholders understand:
• How much testing was performed
• How many test cases were executed
• How many defects were identified and fixed
• Whether the software is ready for release
A typical test summary report includes:
• Total number of test cases
• Number of executed test cases
• Number of passed and failed test cases
• Number of defects found and resolved
• Overall testing status
Real-Time Example
Example: Test Summary for Online Shopping System
Item Result
Total Test Cases 120
Executed Test Cases 120
Passed Test Cases 110
Failed Test Cases 10
Defects Fixed 8
Remaining Defects 2
Based on this report, project managers decide whether the software is ready for release or
requires additional testing.
Importance of Test Reporting
• Provides clear information about testing progress
• Helps track defects and test results
• Assists project managers in decision making
• Improves communication among team members
• Ensures software quality before release