black-box testing

Concept

Black-box testing, as evidenced in model-based microprocessor conformance work, is a testing scenario in which an abstract description of the system under test is used to generate tests and to check externally observable conformance, independent of internal implementation details.

First seen 5/25/2026

Last seen 6/8/2026

Evidence 3 chunks

Wiki v2

WIKI

Definition

In the cited microprocessor conformance case study, black-box testing is described as a scenario where an abstract description of the system under test (SUT) is used as the basis for test generation [aecb3458]. The goal is to check that the implementation behaves as described by the abstract model, independently of internal implementation details [aecb3458]. The concept is listed as an explicit keyword of the case study alongside White-Box Testing [11aee6c9, f8849d84].

Role in Model-Based Test Generation

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

1 connections

Test Program Generation for a Microprocessor: A Case-Study ← uses 100% 3e

The paper uses black box testing concepts as part of its testing approach.

LINKED ENTITIES

1 links

Test Program Generation for a Microprocessor: A Case-Study USES Extracted graph relationship

CITATIONS

8 sources

8 citations — click to expand

[1] Black-box testing is a scenario where an abstract description of the system under test is used as the basis for test generation, checking that the SUT behaves as described in the abstract model independently of internal implementation details. Test Program Generation for a Microprocessor: A Case Study

[2] The assembler model is more abstract than the processor model, making details such as interrupt handling, virtual memory and caching, pipelining, and instruction reordering transparent. Test Program Generation for a Microprocessor: A Case Study

[3] In unit testing, the test specification is described by pre- and post-conditions on inputs and results, with control over the initial state and access to internal states after the test; in sequence testing, only initialization of the internal state is necessary, and the test result is inferred from a sequence of system inputs and observed outputs. Test Program Generation for a Microprocessor: A Case Study

[4] A test case is composed of an instruction, an initial configuration, and the resulting configuration after execution; the conformance relation `_ =k _` compares the content of registers and the top k memory cells. Test Program Generation for a Microprocessor: A Case Study

[5] Test program generation is well suited for validating COTS processors for which implementation details are usually unavailable, by generating low-level programs that are run against the processor under test. Test Program Generation for a Microprocessor: A Case Study

[6] The case study uses HOL-TestGen, a model-based testing environment extending Isabelle/HOL, to synthesize test programs that were run against real hardware in the loop. Test Program Generation for a Microprocessor: A Case-Study

[7] The paper's listed keywords explicitly include 'Black Box Testing' alongside 'White Box Testing', 'Theorem Proving', and 'Interactive Testing'. Test Program Generation for a Microprocessor: A Case-Study

[8] The authors applied unit and sequence testing to four instruction categories: memory-related load/store operations, arithmetic operations, logic operations, and control-flow operations. Test Program Generation for a Microprocessor: A Case Study