Expand description
Reusable semantic conformance tests for [virtio_accel_core::Accelerator] backends.
The suite depends only on the transport-independent backend contract. An implementer supplies a
fresh-backend factory, one executable target fixture, and a small hook that advances an event to
completion. Optional accounting lets the same cases detect leaked provider resources. The
numerics module adds stable, device-neutral TOSA graphs and numerical oracles that host
backends can execute without substituting provider-specific fixtures.
Modules§
- numerics
- Device-neutral numerical acceptance cases for hardware backends.
Structs§
- Binding
Fixture - One observable program binding used by the standard execution cases.
- Case
Result - Result for one independently constructed backend instance.
- Conformance
Report - Aggregate result from the standard semantic backend suite.
- Program
Fixture - Provider artifact accepted by the backend under test.
- Resource
Counts - Provider-owned resource totals sampled by an optional accounting hook.
- Submission
Path Diagnostics - Provider-reported submission path counters used to separate real accelerator work from staging.
- Target
Description - Owned provider-specific data required by the transport-free standard suite.
Enums§
- Case
Requirement - Why a conformance case is required or conditional.
- Case
Status - Outcome of one stable conformance case.
- Skip
Reason - Explicit reason that one conditional case did not run.
- Target
Description Error - Invalid provider fixture supplied to the conformance suite.
Traits§
- Conformance
Hooks - Provider-specific control needed by tests without weakening the [
Accelerator] contract.
Functions§
- run
- Run every mandatory and advertised capability-conditional semantic case.