Skip to content
STIMSMITH

Black Box Test Specification

Concept WIKI v1 · 7/18/2026

In directed testing, a black box test specification is a document written in advance by the verification team, based solely on the device under test (DUT) specification, that aims to cover all stated functionality of the DUT. It serves as the foundation from which directed tests are derived, aids in reviewing the DUT spec, and is complemented by a separate test bench specification describing testbench features. Tests derived from the black box test specification are typically insufficient to achieve structural coverage targets, so additional white-box tests are added.

Overview

A black box test specification is a document produced as part of a directed-testing methodology. It is authored by the verification engineers based on their understanding of the device under test (DUT) specification, without relying on knowledge of the DUT's internal implementation. The specification aims to fully exercise the functionality described in the DUT specification.

Role in Directed Testing

In the directed-testing flow:

  1. A separate verification team writes the test specification and a test bench description to provide an independent interpretation of the DUT spec.
  2. The black box test specification is written from the verification engineers' understanding of the DUT specification.
  3. The document aims to test fully all of the stated functionality in the DUT spec, and it is from this specification that the directed tests are written.
  4. The writing of the test specification acts as a thorough review of the DUT spec and can uncover discrepancies or holes in it.
  5. A complementary test bench specification describes the testbench features so that tests can exercise all of the design features and allow for the implementation of the test specification.
  6. Both specifications are reviewed jointly by the design and verification teams, who may suggest additional scenarios.

Coverage Considerations

Tests derived from the black box test specification are typically insufficient to reach structural coverage targets such as branch and toggle coverage. Once structural-coverage targets are not met, additional tests are specified and implemented using a white-box approach, in which a designer and verification engineer examine coverage holes and specify specific transaction sequences to hit the previously uncovered holes, resulting in a set of very targeted tests.

Related Techniques

  • Directed Testing: The verification methodology within which the black box test specification is produced; the specification is the input from which directed tests are derived.

LINKED ENTITIES

1 links
Directed Testing USES

CITATIONS

4 sources
4 citations
[1] The test specification is written using a black box approach from the verification engineers' understanding of the DUT spec, aiming to fully cover all stated functionality. A Comparison of Three Verification Techniques: Directed Testing, Pseudo-Random Testing and Property Checking
[2] Writing the test specification serves as a review of the DUT spec and can uncover discrepancies or holes in it. A Comparison of Three Verification Techniques: Directed Testing, Pseudo-Random Testing and Property Checking
[3] A separate test bench specification is written describing the testbench features so tests can exercise all design features and allow implementation of the test specification; both specs are reviewed by the design and verification teams. A Comparison of Three Verification Techniques: Directed Testing, Pseudo-Random Testing and Property Checking
[4] Tests derived from the black box test spec are insufficient to reach structural coverage targets, so additional white-box tests are specified to target coverage holes. A Comparison of Three Verification Techniques: Directed Testing, Pseudo-Random Testing and Property Checking