Hardware Integration Testing

Definition

Hardware integration testing is the incremental integration testing of two or more integrated hardwareware components in a single environment to produce failures caused by interface defects.

Objectives

The typical objectives of hardware integration testing are to:

Cause failures involving the interactions of the integrated hardware components when running on a single platform.
Report these failures to the hardware development team so that the underlying defects can be identified and fixed.
Help the hardware development team to stabilize the hardware so that it can be successfully distributed prior to system testing.
Minimize the number of low-level defects that will prevent effective system and launch testing.

Preconditions

Hardware integration testing can typically begin when the following preconditions hold:

The integration team is adequately staffed and trained in hardware integration testing.
The integration environment is ready.
The first two hardware components have:
- Passed unit testing.
- Been ported to the integration environment.
- Been integrated.

Completion Criteria

Hardware integration testing is typically complete when the following postconditions hold:

A test suite of test cases exists for each interface between hardware components.
All hardware integration test suites successfully execute (i.e., the tests completely execute and the actual test results match the expected test results).

Tasks

Hardware integration testing typically involves the integration team performing the following testing tasks:

Environments

Hardware integration testing is typically performed on the following environments using the following tools:

Integration Environment
- Test Harness

Phases

Hardware integration testing consists of the following tasks being performed during the following phases:

PHASE → TASK ↓	Business Strategy	Business Optimization	Initiation	Construction	Delivery	Usage	Retirement
Test Planning	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable
Test Reuse	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable
Test Design	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable
Test Implementation	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable
Test Execution	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable
Test Reporting	Not Applicable	Not Applicable	Started	Completed	Iterated	Iterated	Not Applicable

Guidelines

The iterative and incremental development cycle implies that hardware integration testing is regularly performed in an iterative and incremental manner.
Hardware integration testing can elicit failures produced by defects that are difficult to detect during system or launch testing once the system has been completely integrated.