assertSE primitive

CodeArtifact

The `assertSE` primitive is a state-exception primitive used in generated VAMP microprocessor test specifications to express post-conditions over the final automaton state after executing instruction sequences.

First seen 5/26/2026

Last seen 5/26/2026

Evidence 2 chunks

Wiki v1

WIKI

Overview

assertSE is used in the VAMP microprocessor test-generation case study as a state-exception primitive for expressing test post-conditions on the final state of an automaton. In the shown specifications, an instruction sequence is executed with mbind ... execVAMP, and assertSE checks a predicate over the resulting state, typically comparing that state with the result produced by the system under test (SUT) for the same initial state and instruction sequence. [C1]

Typical form

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

state-exception monad implements → 90% 1e

assertSE is a primitive of the state-exception monad used for post-condition checking.

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

The paper uses assertSE to express test post-conditions.

CITATIONS

6 sources

6 citations — click to expand

[1] assertSE is a state-exception primitive used to express test post-conditions on the final state of the automaton. Test Program Generation for a Microprocessor: A Case Study

[2] Generated test specifications execute instruction sequences with mbind and execVAMP and then apply assertSE to a predicate over the final state comparing it with the SUT result. Test Program Generation for a Microprocessor: A Case Study

[3] For load/store sequence tests, gen_test_data instantiates schematic variables with concrete values and the resulting test ends with assertSE. Test Program Generation for a Microprocessor: A Case Study

[4] Arithmetic and branch sequence examples both use assertSE after executing generated instruction lists. Test Program Generation for a Microprocessor: A Case Study

[5] Using assertSE for final-state post-conditions is described as not very realistic for hardware processors because the final state, especially internal processor registers, is not directly observable. Test Program Generation for a Microprocessor: A Case Study

[6] The source proposes the state-exception primitive return as an alternative for step-by-step checking of output values, requiring a modified VAMP with trusted wrappers exposing internal register content. Test Program Generation for a Microprocessor: A Case Study