unit testing

Concept

Unit testing, in the provided model-based testing evidence, is a testing scenario in which a test specification is expressed with pre- and post-conditions over the inputs and results of the system under test. It assumes control over the initial state and access to the system's internal state after the test, and it can be viewed as a special one-step form of sequence testing.

First seen 5/25/2026

Last seen 5/26/2026

Evidence 4 chunks

Wiki v1

WIKI

Definition

In the cited model-based testing setting, unit testing is a scenario where the test specification is described by pre-conditions and post-conditions on the inputs and results produced by the system under test (SUT). This scenario assumes control over the initial state and access to the internal states of the SUT after the test. [C1]

Relationship to sequence testing

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% 2e

The paper applies unit testing scenarios to test individual instructions.

LINKED ENTITIES

1 links

sequence testing SPECIALIZATION_OF Extracted graph relationship

CITATIONS

7 sources

7 citations — click to expand

[1] Unit testing is described by pre- and post-conditions on inputs and results and assumes control over the initial state plus access to the SUT internal state after the test. Test Program Generation for a Microprocessor: A Case Study

[2] Unit testing can be seen as a special 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

[3] A general unit instruction test specification compares the SUT result with model execution using an executable conformance equality over registers and the top k memory cells. Test Program Generation for a Microprocessor: A Case Study

[4] Each unit test case in the case study is composed of an instruction, an initial configuration, and the resulting configuration after instruction execution. Test Program Generation for a Microprocessor: A Case Study

[5] HOL-TestGen produces tests from the specification, and instruction subsets are isolated by adding pre-conditions specifying instruction type. Test Program Generation for a Microprocessor: A Case Study

[6] The VAMP case study uses unit testing to test individual operations or instructions with different data and sequence testing for instruction sequences up to a given length, covering load/store, arithmetic, logic, and control-flow instruction types. Test Program Generation for a Microprocessor: A Case Study

[7] Pre-conditions are also called test purposes and are used to reduce generated instruction sequences to a given subset; the is_load_store predicate restricts a scenario to load/store operations. Test Program Generation for a Microprocessor: A Case Study