Test Harness (TH)

Definition

A test harness is a testing work product modeling a software tool that automates the testing process by running test suites of test cases.

Objectives

The typical objectives of a test harness is to:

• Automate the testing process.
• Execute test suites of test cases.
• Generate associated test reports.

Benefits

A test harness typically provides the following benefits:

• Increased productivity due to automation of the testing process.
• Increased probability that regression testing will occur.
• Increased quality of software components and application.

Contents

Not relevant.

Stakeholders

• Producers:
  • Independent Test Team
  • Programmer
• Evaluator: Test Inspection Team
• Approvers:
  • Technical Leader
  • Project Manager
  • Independent Test Team
• Maintainers:
  • Independent Test Team
  • Programmer
• Users:
  • Software Development Test Team uses the test harness to automate the unit and software integration testing process.
  • Independent Test Team uses the test harness to automate the system and launch testing process.

Phases

• Initiation: Not Applicable
• Construction: Completed and Maintained
• Delivery: Completed
• Usage: Maintained
• Retirement: Archived

Preconditions

A test harness can typically be started if the following preconditions hold:

• The relevant sections of the Project Test Plan is completed.
• The relevant team is staffed.

Inputs

• Work Products:
  • Project Test Plan
  • System Requirements Specification
  • Project Environments Description Document
• Stakeholders:
  • Test tool vendor technical representative

Guidelines

• Use commercial off the shelf (COTS) test tools where practical.

Conventions

A test harness is typically constrained by the following conventions:

• None.