CH-03

Test Management
 Test Planning
• Preparing a Test Plan
• While Preparing a Test plan, it should acts as
execution, tracking and reporting of the entire testing
of project and it should cover:
• The Scope of Testing,
• How the testing is going to be performed,
• What Resources are needed for testing,
• The TimeLine,
• Risk factor
• Scope Management
• Scope Management specifies the scope of a project.
• For testing, Scope Management entails,
1.Understanding what constitutes a release of a product;
2.Breaking down the release into features;
3.Prioritizing the features for testing;
4.Deciding which feature will be tested and which will not be;
5.Gathering details to prepare for estimation of resources for testing.

• The following factors drive the choice and prioritization of features to

be tested.
• Feature that are new and critical for the release.
• Feature whose failures can be catastrophic.
• Feature that are expected to be complex to test.
• Features which are extensions of earlier features that have been defect
prone.
• Deciding Test Approach
• Deciding Test Approach include identifying
1. What type of testing would you use for testing the functionality?
2. What are the configurations or scenarios for testing the features?
3. What integration testing would you do to ensure these features work together?
4. What localization validations would be needed?
5. What “non-functional” tests would you need to do?

• Setting Up Criteria for Testing

• A test cycle or a test activity will not be an isolated, it is a
continuous activity that can be carried out at one go. Some of the
typical criteria include,
1. Encountering more than a certain number of defect
2. Hitting a show stoppers that prevent further progress of testing
3. Developers releasing a new version which they advise should be used in lie of
the product under test.
• Identifying Responsibilities, Staffing and Training
Needs
• Identifying Responsibilities, Staffing and Training
Needs addresses the aspects of test planning i.e. who
part of it. A testing project require different people to
play different roles, So the different role definitions
should
1. Ensure clear accountability for a given task;
2.Clearly list the responsibilities for various functions to
various people;
3. Complement each other;
4. Supplement each other;
• Resource Requirements
• Project Manager should provide estimates for the various hardware
and software resource required. Some of the following factors need to
be considered.
1. Machine configuration,
2. Overheads required by the test automation tool,
3. Supporting tools such as Compiler, Test data generator, Configuration management
tool.
4. The different configurations of the supporting software,
5. Special requirement for running machine-intensive tests
6. Appropriate number of licenses of all the software.

• Test Deliverables
• The deliverables include the following,
1. The test plan
2. Test case design specification
3. Test case
4. Test logs produced
5. Test summary report
• Testing Tasks (Size and Effort Estimation)
• Estimations happens broadly in three phases,
1. Size estimation
• -Number of test cases
• -Number of test scenarios
• -Number of configuration to be tested

2. Effort estimation
• -Productivity data
• -Reuse opportunities
• -Robustness of processes

3. Schedule estimation
 Test Management
• Choice of Standards
Internal Standard include,
1. Naming and storage conventions for test artifacts;
2. Document standards;
3. Test coding standards;
4. Test reporting standards.
• Test Infrastructure Management
• Testing requires a robust infrastructure to be planned
upfront. This infrastructure is made up of three
essential elements.
• 1. A test case database (TCDB)
• 2. A defect repository
• 3. Configuration management repository and tool
• A test case database captures all the relevant
information about the test cases in an organization.
• A defect repository captures all the relevant details of
defects reported for a product.
• TCDB, defect repository and SCM repository should
complement each other and work together in an
integrated fashion
• Test People Management
• People management is an integral part of any project
management.
• People management also requires the ability to hire,
motivate, and retain the right people.
• Testing projects present several additional challenges.
• We believe that the success of a testing organization
depends vitally on judicious people management skills
 • Integrating with Product Release
• The success of a product depends on the effectiveness of
integration of the development and testing activities.
• The schedules of testing have to be linked directly to product
release.
• The following are some of the points to be decided for this
planning-
1. Sync point between development and testing as to when different
types of testing can commence.
2. Service level management between development and testing as to
how long it would take for the testing team to complete the testing.
3. Consistent definitions of the various priorities and severities
of the defects.
4. Communication mechanisms to the documentation group to
ensure that the documentation is kept in sync with the product in
terms of known defects.
 Test Process
• Base Lining a Test Plan
• A test plan combines all the points into a single
document that acts as an anchor point for the
entire testing project.
• An organization normally arrives at a template
that is to be used across the board. Each testing
project puts together a test plan based on the
template.
• The test plan is reviewed by a designated set of
component (people) in the organization.
• After this, the test plan is baselined into the
configuration management repository.
• then the baselined test plan becomes the basis for
running the testing project.
• In addition, periodically, any changes needed to
the test plan templates are discussed among the
different stake holders and this is kept current
and applicable to the testing teams.
Test Case Specification
• Using the test plan as the basis, the testing team
designs test case specification, which then
becomes the basis for preparing individual test
cases. Hence, a test case specification should
clearly identify,
1. The purpose of the test: This lists what features or
part the test is intended for.
2. Items being tested, along with their version/release
numbers as appropriate.
3. Environment that needs to be set up for running the
test cases: This includes the hardware environment
setup, supporting software environment setup, setup of
the product under test.
4. Input data to be used for the test case: The choice of
input data will be dependent on the test case itself and
the technique followed in the test case.
5. Steps to be followed to execute the test: If
automated testing is used, then, these steps ate
translated to the scripting language of the tool.
6. The expected results that are considered to be
“correct result”.
7. A step to compare the actual result produced with
the expected result: This step should do an
“intelligent” comparison of the expected and actual
results to highlight any discrepancies.
8.Status of the Test Case.
Update of Traceability
• a requirements traceability matrix ensures that the
requirements make it through the subsequent life
cycle phases and do not get orphaned mid-course.
• - The traceability matrix is a tool to validate that
every requirement is tested.
• - The traceability matrix is created during the
requirement gathering phase itself by filling up the
unique identifier for each requirement.
• -This ensures that there is a two-way mapping
between requirements and test cases.
Matrix
• A matrix is a concise organizer of simple tests,
especially useful for function tests and domain
tests. It groups test cases that are essentially the
same. For example, for most input fields, you’ll do
a series of the same tests, checking how the field
handles boundaries, unexpected characters,
function keys, etc.
• To create a test matrix, you will have to:
• Put the objects that you’re testing on the rows.
• Show the tests on the columns.
• Check off the tests that you actually completed in
the cells.
Executing Test Cases
• The prepared test cases have to be executed at
the appropriate times during a project.
• As the test cases are executed during a test cycle,
the defect repository is updated with:-
1. Defect from the earlier test cycles that are fixed
in the current build;
2. New defect that get uncovered in the current run
of the tests.
As and when tests get designed and executed
successfully, the traceability matrix should be
updated.
 Test Reporting
Recommending Product Release.

• Based on the test summary report, an organization

can take a decision on whether to release the
product or not.
• Ideally, an organization would like to release a
product with zero defects.
• However, market pressures may cause the product
to be released with the defects provided that the
senior management is convinced that there is no
major risk of customer dissatisfaction.
• Such a decision should be taken by the senior
• Collecting and Analyzing Metrics
• When test are executed, information about test
execution gets collected in test logs and other files.
converted to meaningful metrics.
• Preparing Test Summary Report
• At the completion of a test cycle, a test summary
report is produced. This report gives insights to the
senior management about the fitness of the product
for release. There are two types of reports that are
required:
1. The Incident Report
2. Test Cycle Report
3. Test Summary Report
• Test reporting is a means of achieving communication
through the testing cycle.
There are 3 types of test reporting.
1. Test incident report:
• A test incident report is communication that happens
through the testing cycle as and when defects are
encountered .
A test incident report is an entry made in the defect
repository each defect has a unique id to identify incident .
Test cycle report:
• A test cycle entails planning and running certain
test in cycle , each cycle using a different build of
the product .
• As the product progresses through the various
cycles it is expected to stabilize.
• Test cycle report gives
• 1. A summary of the activities carried out during
that cycle.
• 2. Defects that are uncovered during that cycle
based on severity and impact
• 3. Progress from the previous cycle to the current
cycle in terms of defect fixed
 • Test summary report:
• The final step in a test cycle is to recommend
the suitability of a product for release.
• A report that summarizes the result of a test
cycle is the test summary report.
• There are two types of test summary report:
1.Phase wise test summary ,which is produced at
the end of every phase
2. Final test summary report .
 • A Summary report should present
1. A summary of the activities carried out during the test
cycle
2 Description :Identify the test items being reported in
this report with test id
3 Variances: Mention any deviation from test plans, test
procedures, if any.
4 Summary of results: Summary of results should
include tests that failed and severity of impact of defect;
5 Comprehensive assessment and recommendation for
release should include Fit for release assessment and
recommendation of release