conformance testing

Concept

Conformance testing, as evidenced in the VAMP microprocessor case study, checks whether a system under test behaves according to an abstract model. In that study, tests are generated from the formal assembly-level instruction-set model and used to compare the gate-level processor implementation against the model, using unit and sequence testing scenarios.

First seen 5/25/2026

Last seen 6/6/2026

Evidence 7 chunks

Wiki v1

WIKI

Overview

In the VAMP microprocessor case study, conformance testing is framed as checking that a processor behaves as described by an abstract assembler model, independently of internal implementation details. The study uses an abstract description of the system under test as the basis for test generation in a black-box testing scenario. In the hardware-layer setting, tests are generated from the formal assembly-level instruction-set model and used to test the conformance of the gate level to the assembly level. [C1]

Conformance relation

READ FULL ARTICLE →

NEIGHBORHOOD

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

explore full graph →

RELATIONSHIPS

2 connections

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

The paper develops conformance test scenarios for a microprocessor.

Tandem Simulation ← implements 87% 1e

Tandem simulation is an improvement over traditional conformance testing

LINKED ENTITIES

3 links

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

model-based test case generation APPLIES Extracted graph relationship

stuck-at-fault model USED_IN Extracted graph relationship

CITATIONS

7 sources

7 citations — click to expand

[1] In the VAMP case study, conformance testing checks that the processor behaves as described by the assembler model independently of internal implementation details, and tests gate-level behavior against the assembly-level model. Test Program Generation for a Microprocessor: A Case Study

[2] The `_ =k _` conformance relation compares the model-controlled state and SUT-controlled state by checking register contents and the top `k` memory cells, relying on a trusted test environment to abstract the external state. Test Program Generation for a Microprocessor: A Case Study

[3] The study applies model-based unit testing and sequence testing, with unit testing based on pre/postconditions and sequence testing based on initialized internal state and observed input/output behavior. Test Program Generation for a Microprocessor: A Case Study

[4] Unit test cases consist of an instruction, an initial configuration, and a resulting configuration; HOL-TestGen produces tests, and preconditions isolate instruction subsets. Test Program Generation for a Microprocessor: A Case Study

[5] For sequence testing, the relevant scenario in the case study checks the final state, either over the entire state or a selected part such as register 0; preconditions, also called test purposes, reduce generated instruction sequences. Test Program Generation for a Microprocessor: A Case Study

[6] The conformance-testing setup is model-based and uses HOL-TestGen on Isabelle/HOL, with phases for test-case generation, test-data selection, and test execution. Test Program Generation for a Microprocessor: A Case Study

[7] The paper contrasts its model-based approach with stuck-at-fault techniques, which it characterizes as white-box mutation techniques based on fabrication fault models and notes may miss design flaws such as byte-alignment-related write-read errors. Test Program Generation for a Microprocessor: A Case Study