Software Testing(22518)

TEST MANAGEMENT

Test Planning

Test Management

Test Process

Test Reporting
 Software Testing(22518)
TEST MANAGEMENT

Test Planning

Preparing a test plan

Deciding Test Approach

 Software Testing(22518)
TEST PLAN describes
Scope
Approach
Resources
Schedule
 Software Testing(22518)
TEST MANAGEMENT
Preparing a test plan
1.Analyze the product
2.Develop Test strategy
3.Define objectives of testing
4.Define test Criteria
5.Planning the resources
6.Plan test Environment
7.Schedule and cost
8.Test Deliverables.
 Software Testing(22518)
TEST PLAN Types
1.Master Test Plan
2.Testing level specific test plan.
a. Unit test plan
b. Integration Test plan
c. System test plan
d. Acceptance Test plan
3.Testing Type specific test plan.
a. Performance Test Plan
b. Security Test Plan
 Software Testing(22518)
TEST MANAGEMENT
Test management is the practice of organizing and controlling the process and
artifacts required for the testing effort.

Tools used for test management

1.Pen & Paper
2.Word processors
3.Spreadsheets.
 Software Testing(22518)
TEST MANAGEMENT

Setting up criteria for Testing

Identifying Responsibilities

Staffing

Resource Requirements.
 Software Testing(22518)
TEST MANAGEMENT
Setting up criteria for Testing
1.Entry Criteria
2. Exit Criteria
3. Pass or Fail Criteria
4. Suspend Criteria
5. Resume Criteria
Types of Standards

External Standards

Customer Standards

National

International Standards

Internal Standards
 Software Testing(22518)
TEST MANAGEMENT
Test infrastructure management
Components
1.Required hardware infrastructure
2.Required software infrastructure
3.Required automated testing tools infrastructure
 TCDB

Test case
info
Test case Test case
product XREF
defect XREF
Test case
info

SCM DR

Pproject Defect
test cases details
Defect
Environment product Defect fix communicat
files source code ions
details

product Defect test

documentation details
 TCDB(TEST CASE DATABASE)
ENTITY PURPOSE ATTRIBUTES

Test case Records all the static information about the test Test case ID , Test case name(filename),test case
owner
Associated files for the test case.

Test case-product cross Provides a mapping between the tests and the corresponding Test case ID , Modulate ID
reference product features; enables identification of tests for a given
features.

Test case-run history Gives the history of when a test was run and what was the Test case ID ,Run date ,time taken ,Run status
result; provides inputs on the selection of tests for regression (success/failure)
runs.

Test case-Defect cross Gives details of test cases introduced to test certain specific Test case ID defect reference#
reference defects detected in the product ;provides inputs on the
selection of tests for regression runs.
 Defect Repository
ENTITY PURPOSE ATTRIBUTES

Defect Details Records all the static information about the test Defect ID , defect priority/severity, defect
description, Affected product.

Defect test details Provides details of test cases for a given defect. cross Defect ID,Test case ID .
references the TCDB.

Test case-run history Gives the history of when a test was run and what was the Test case ID ,Run date ,time taken ,Run status
result; provides inputs on the selection of tests for regression (success/failure)
runs.

Test case-Defect cross Gives details of test cases introduced to test certain specific Test case ID defect reference#
reference defects detected in the product ;provides inputs on the
selection of tests for regression runs.
 Software Testing(22518)
TEST PROCESS STEPS:----
1.Test planning and control
2.Test analysis and design
3.Test implementation and execution
4.Evaluation of exit criteria and test reporting
5.Test closure activities.
 Software Testing(22518)
Collecting and Analyzing metrics
1.Requirement volatility
Formula=(no.of requirements added+no.of requirements deleted+
no.of requirements modified)/(no.of initial approved
requirements)*100

Unit of measure=percentage
 Software Testing(22518)
2.Review efficiency
Formula=(no.of weighted review defect/effort spent on reviews)

Unit of measure=defect per person hour

3.Productivity in test execution

Formula=(no.of test cases executed/time spent in test execution)

Unit of measure=test cases per person per day

 Software Testing(22518)
1.Defect rejection ratio
Formula=(no.of defects rejected/total no.of defects raised)*100

Unit of measure=percentage

2.Defect fix rejection ratio

Formula=(no.of defects fixes rejected/total no.of defects fixed)*100

Unit of measure=percentage
 Software Testing(22518)
3.Delivered defect density
Formula=(no.of weighted defects found during validation/customer
reviews+acceptance testing)/(size of the work product)

Unit of measure=Defect for the work product/cycle

4.Outstanding defect ratio

Formula=(total number of open defects/total number of defects
found)*100
Unit of measure=percentage
 Software Testing(22518)
Preparing test summary report

1.Purpose of the document

2.Overview of an application

3.Testing scope

4.Metrics

5.Types of testing performed

Preparing test summary report

6.Information of test environment and tool

7.Lesson learned

8.Recommendations

9.Best practices

10.Exit criteria

11.conclusion/sign off
Types of test reports

1.Test incident report

2.Test cycle report(summary report)