Black-Box Testing
ConceptBlack-box testing is a testing scenario in which an abstract description of the system under test (SUT) is used as the basis for test generation, with the goal of checking externally observable conformance independently of internal implementation details. In the SoC domain, post-silicon validation is explicitly identified as a form of black-box testing with limited internal visibility, and in the model-based testing domain it underpins conformance test programs generated from abstract processor models and run against real hardware.
First seen 5/25/2026
Last seen 6/16/2026
Evidence 4 chunks
Wiki v3
WIKI
Definition
Across the cited evidence, black-box testing is characterized by what is observable rather than by what is known internally about the system under test (SUT). Two complementary characterizations appear in the sources:
- In the microprocessor conformance case study (Brucker et al.), a black-box testing scenario is one in which an abstract description of the SUT is used as the basis for test generation, and the aim is to check that the implementation behaves as described by the abstract model, independently of the internal implementation details [aecb3458].
- In the SoC validation literature, post-silicon validation of a manufactured chip is identified as a form of black-box testing because it has limited visibility into the design, in contrast to pre-silicon validation, which is described as a white-box testing setting with high visibility into the design for debugging [18bd92ff].
NEIGHBORHOOD
No graph connections found for this entity yet. It may appear in future ingestion runs.
explore full graph →RELATIONSHIPS
1 connectionsThe paper uses black box testing concepts as part of its testing approach.
LINKED ENTITIES
1 linksCITATIONS
12 sources12 citations — click to expand
[1] In a black-box testing scenario, an abstract description of the system under test is used as the basis for test generation, with the aim of checking that the implementation behaves as described by the abstract model, independently of the internal implementation details. Test Program Generation for a Microprocessor: A Case Study
[2] Post-silicon validation of a manufactured chip is also known as black-box testing, has limited visibility in the design, and makes failure debugging laborious and time-consuming. Unified Coverage Methodology for SoC Post-Silicon Validation
[3] Pre-silicon validation, also called white-box testing, allows high visibility into the design for debugging but limits simulation speed and thus the number of tests. Unified Coverage Methodology for SoC Post-Silicon Validation
[4] The assembler model in the case study abstracts over interrupt handling, virtual memory and caching, pipelining, and instruction reordering, and the processor model is used to extract abstract test cases for the processor. Test Program Generation for a Microprocessor: A Case Study
[5] On-chip coverage monitoring hardware can increase observability in post-silicon validation, but does not contribute to functional logic and is therefore controlled and limited. Unified Coverage Methodology for SoC Post-Silicon Validation
[6] Sequence testing infers results from sequences of inputs and observed outputs and only requires initialization of the internal state, while unit testing is a one-step form of sequence testing where the output state is more or less completely accessible. Test Program Generation for a Microprocessor: A Case Study
[7] The conformance relation _ =k _ compares register content and only the top k memory cells, and a test case consists of an instruction, an initial configuration, and the resulting configuration after execution. Test Program Generation for a Microprocessor: A Case Study
[8] Test program generation is especially suitable for validating commercial off-the-shelf (COTS) processors, for which implementation details are usually unavailable. Test Program Generation for a Microprocessor: A Case Study
[9] A theory of black-box tests characterizes the requirements that can be refuted (and, dually, verified) through black-box testing, obtains finite falsifiability of hyper-safety temporal requirements as a special case, and separates refutation from enforcement under computational constraints. A Theory of Black-Box Tests
[10] Three algorithms for equivalence, identity, and unitarity checking have been proposed specifically for black-box testing of quantum programs, together with optimization techniques and parameter-selection guidance. Equivalence, Identity, and Unitarity Checking in Black-Box Testing of Quantum Programs
[11] HOL-TestGen, a model-based testing environment that is an extension of Isabelle/HOL, is used to synthesize test programs that are run against real hardware in the loop. Test Program Generation for a Microprocessor: A Case-Study
[12] The case study applied unit and sequence testing scenarios to four categories of instructions: memory-related load/store operations, arithmetic operations, logic operations, and control-flow operations. Test Program Generation for a Microprocessor: A Case Study