Test Management

 Test policy
 Test Strategy
 Test Planning
 Test Scenario Definition
 Test Cases Definition
 Test Data Definition
Test plan is a strategic document which describes how to
perform a task in an effective and optimized way

Steps in Test Plan

1. Set objectives of test plan

2. Develop a test matrix

3. Develop test administrative component

4. Write the test plan
 Determine scope and risks
 Documenting Test Strategy.
 Making sure about test activities have been included
 Deciding entry and exit criteria
 Evaluate Test estimation
 The test artefacts delivered as part of execution
 Defining management information
 Make sure that test documentation involves repeatable
tests
1) Test Plan
2) Preparing a Test plan
3) Scope management
4) Deciding Test Approch /Strategy
5) Setting up criteria for testing
6) Identifying responsibility
7) Staffing and Training Needs
8) Resource Requirements
9) Identifying Test Deliverables
10) Testing Tasks(Size & Effort Estimation)
11) Schedule
➢ A test plan is a document describing software Testing scope ,
approch , schedule, resource and activities.

➢ It is the basis for formally testing any software in the project.

➢ A document describing the scope, approach, and schedule of
intended test activities.
➢ In this documentation of features to be tested, testing task, test
design techniques, entry and exit criteria.
➢ It is a record of planning process.
There are two types of plans
Master test plan
A plan that typically consists addresses different test
levels.
Phase test plan
A plan that typically consist one test phase.
 Testing Process
 Requirement Traceability
 Tested Items
 Testing Schedule
 Test Recording Procedures
 H/W and S/W Requirements
 Constraints
 System Tests
1. Test plan identifier: unique number to identify test
plan.
e.g. project_name001
2. References: supportive documents for test plan.
e.g SRS
Use case documents, test strategy, test plan.
3. Introduction : Purpose and scope of the project.
To test functionality of the project name.
4. Test items: A list of test items which will be tested.
5. Features to be tested: login functionality, dashboard,
reports.
6. Features not to be tested:
7. Test approach: Test types, test techniques.
8. Setting up criteria for pass/fail
9. Suspension criteria: login functionalities or major
functionalities not performed.
10. Test deliverables :bug report.
11. Testing task : test environment, test execution, test
summary report.
12. Resource requirement.
13. Identifying responsibilities.
14. Staffing and training needs.
15. Schedule
16. Risk
17. Approval
18.Glossary: (Summary)
Test Plan is deals with objectives of a software.
The test plan acts as an anchor for execution of entire
software
Following points are followed while preparing a Test Plan:
1.What is to be tested?
2.How testing will be performed?
3.Which resources are needed?
4.When each test will occurs?
5.Which will be deadline for testing?
6.Risks that may be faced through out testing.
➢ The Scope describes the activities included and
excluded from quality assurance/quality control
activities.
➢ Scope of the test includes what items, features ,
procedures , functions ,objects , will be tested
➢ Test Scope includes:

1.Functional/Structural Requirements
2.Infrastucture Components
3.Application Components
4.System Interface
Feature to be considered in scope management:
1.Features that is new and critical for release
2.Features whose failures can be disastrous
3.Features that are expected to be complex to test
4.Features which are extensions of earlier features
 Test Approach/Strategy should result in identifying the
right type of test for each of the features.
 This includes identifying:
 Which tools to be used?
 Will that tool require special training?
 Which metrics to be collected and at what level?
 How many configurations will be tested?
 H/W and S/W
 Test strategies decide how to test these features and
combinations would be tested.
 To avoid last minute pressure of executing tests after
development.
 The Entry criteria for a test specify threshold criteria
for each phase.
 Exit criteria decide when a cycle can be completed.
 Number of times it is suspended because it is not
proceed further.
 When situation comes under control it will be resumed.
 Some of the typical suspension criteria include:
1.Encountering more than a certain number of defects
2.Hitting show stoppers that make difficult further
progress of testing.
3.Developers releasing new version should be used
 Fix responsibilities to different individuals .(Project
Manager,Leader,Programmer,Tester)
 Some Responsibility task are given below:
1.Identify the group responsible for designing , executing ,
checking , managing.
2.Identify the group responsible for providing test items.
3.Identify the group responsible for providing environmental
needs
7. Staffing and Training Needs
There are different roles in testing strategy:
• Test Engineers
• Test Leaders

• Test Managers

8.Resource Requirements:
 Machine configuration like RAM, Processor disk.
 Automation tool.
 Supporting tools like test data generators, configuration
management tools.
 Load tests and performance tests.
 Appropriate number of licenses of all the software
 Test deliverables is the product being delivered and is
normally the software under test.
 Deliverables include following:
1. Test plan document
2. Test cases
3. Test design specifications
4. Tools and their Outputs
5. Simulators
6. Static and Dynamic generators
7. Error logs and execution logs
8. Problem reports and corrective actions
9. Test summary reports.
Estimation in three phases
1. Size Estimation
2. Effort Estimation
3. Schedule Estimation
1. Size of the product under test
2. Extent of Automation required
3. No. of platforms & Inter-operability environments to
be tested
4. Productivity Data
5. Reuse Opportunities
6. Robustness of Processes
1. Size of the product under test
a) Lines of code:
b) Function point:
c) Simpler representation of application size (i.e. Simple,
Medium, Complex)
a) Lines of code:
It depends on:
➢ language used for coding,
➢ respective style of programming,
➢ compactness of programming,
➢ only considered for coding phase.
➢ not for requirement and design.
b) Function point:
 A function point can be widely used to measure the size of software.
 To measure functionality.
 To measure complexity of software.
Parameters for function point

 External input
 External output
 Logical internal files
 External interface files
 External inquiry
1.Date
2.Time
 It is a method of organizing test assets such as test
requirements, test cases, test results.
 It refers to the activity of the managing software testing
process.
 Test management allows different teams to plan,
develop, execute and access all testing activities.
 Standards means it gives uniformity in understanding the
subject for which they written or developed.
 Two Types:
1. External Standards:
a) Customer Standards
b) National Standards
c) International Standards
2. Internal Standards :
a) Naming & Storage Conventions foe test Artifacts
b) Documentation Standards
c) Test Coding Standards
d) Test Reporting Standards
Testing requires robust Infrastructure.
Stronger infrastructure provides stability, continuity,
reliability.
Testing infrastructure made up of 3 essential elements:
1. A Test Code DataBase(TCDB)
2. A Defect Repository
3. A Configuration Management Repository & Tool
1. A Test Code DataBase(TCDB):
TCDB captures all relevant information about the test cases.
2. A Defect Repository:
It captures all relevant details of defects reported for a product.
3. A Configuration Management Repository & Tool
It is a collection of software elements that concerned with
labelling,tracking,comtrolling changes in the software.
A test team: A test team comprise of individuals having
varying
 skill levels.
 experience levels.
 expertise levels.
 different attitudes.
 different expectations/interest levels.
 Success of product depend on Integrating with people
of the development.
Following points to be decided:
1. Sync Points

2. Service Level Agreements

3. Consistancy

4. Communication
 Testing is not a single activity.
 It is a set of number of processes.
Test Process Activities:
1. Base lining a test plan.
2. Test case specification.
3. Update of traceability Matrix
3.3.1. Base lining a test plan:
➢ A Test Plan combines all the points in a single document that
acts as an anchor point for entire project
➢ Each testing project puts together a test plan based on a
template
➢ The baselined test plan becomes basis for successfully running
project.
➢ If any change in a testing project be reflected in a test plan.
3.3.2. Test case specification
 Test case specification describes what scenarios will be tested , how they will
be tested how often they will be tested. It has to be done separately for each
unit.
 It involves:
 a) Purpose of a test plan
 b) Items being tested
 c) Environment that needs to be set up for running test case
 d) Input data used to test case
 e) Steps to be followed to execute the test
 f) The expected result
 g) a step to compare the actual results produced with expected result
 h) Relationship between this test & another Test
3.3.3.Update of Traceability Matrix
 It is a document which contains a table of linking information
used for tracking back for reference in any kind of confusion
or questionable situation
A Test report is any description explanation or justification of
the status of a test project.
Two types of report:
1. Test Incident Report
2. Test Cycle Report
3 .Test Summary Report:
a) Phase-wise Test Summary report
b) Final Test Summary report
A summary report includes:
i) Summary of activities
ii) Variance of activities
iii)Summary of results
iv) Comprehensive Assesment & Recommendation
3.4.1 Recommending Product Release:
Based on summary report an organization takes a
decision whether to release product or not.
Recommending Product Release Criteria:
Checks fitness of product
➢ Which is defect

➢ Severity of defect

➢ Risk of releasing product

3.4.2 Executing Test Cases
 Execute test cases at the appropriate times during a project.
 Defect repository updated with defects with previous test
cycles and updated with defects from previous test cycles
which are fixed in current build.
 Defect repository is communication among with test team and
development team.
 Defect repository defects which are uncovered during testing.
 3.4.2 Executing Test Cases
 Defect repository is reported to stakeholders for current status.
 Communicated with the help of mails, conference calls.
 Test may be suspended at the mid of execution due to
show stopper defects.

Suspended criteria wait still resumption criteria.

Traceability matrix is used while execution of test cases.
 Testing needs communication between test team and other team.
There are two types of communication report:
 Test incident report
 Test summary report.
Test incident report communication which occurs through testing
cycle whenever defects are encountered.
A test incident report is an entry which has been made in the
corresponding defect repository.
 Test Summary Report Identifier : Company generated
unique number that is allocated to this report.
 Summary :After assigning unique id summarize test report.
❖ Test items: Test items should match test items provided in the
definition of test plan.
❖ Test Environment: It should be according to the test plan and
❖ and validate correct set up used by team.
❖ References: Includes any document or evidence that can
support to the report.
➢ Variances : The team documents any deviation or changes
from those areas and plans which were agreed by everyone
from the document.
➢ These includes references supporting the documentation like
change requests, enhancement request , incident report ,test
plan and specifications among other references.
 Comprehensiveness assessment : This involves
evaluation of testing and testing process for determining
quality and effectiveness of testing activities.
To find out weakness and any challenge while executing it.
 Summary of results: It includes impact of testing.
 Resolved incidents and defects.
 Division of these defects as per severity and priority.
 Some of other information included in this document are:
 Nature and cause of problems.
 Cost , impact and positive trends.
 Severity and priority of impact and defects.
 Defect pattern.
 Pass and failure of incident.
 Evaluation :On the basis of evaluation the team offers
information about the testing process, its information,
drawbacks, failure, high and medium risk areas ,good quality
areas and features.
 Summary of activities: It defines testing activities, the time
and efforts invested in it.
 The main focus is on the process , techniques, used to achieve
set goals and requirements, changes in the plan.
 Approval : Approval in the form of signature and
documentation are included by the team provided by testers
These should match the approval provided in the test plan to
verify the result of testing.
Thank You