All Classes and Interfaces
Class
Description
Checks from the JUnit XML reports of a backend that its contract cases really ran (roadmap R2: a CI job that
silently skipped its backend must fail).
A fault a
FaultInjector applies to one store operation (06-stores.md §3).Waits, then performs the operation: a slow store, or a timeout when longer than the caller waits.
Throws without performing the operation: the request never reached the store.
Performs the operation, then throws instead of returning: the response was lost, and a retry replays a request
the store already applied.
The faults a
FaultyRangeStore or FaultySlotLeaseStore applies, per operation: one-shot faults in the
order they were queued, then the standing fault if any.A store operation.
A
RangeStore that applies the faults of a FaultInjector before delegating, for the generator tests
of R1 (delays, timeouts, lost responses).A
SlotLeaseStore that applies the faults of a FaultInjector before delegating, for the lease tests
of R1 (delays, timeouts, a lost renewal response then its replay).The in-memory reference store (06-stores.md §3): passes every contract, for the unit tests of core and Spring.
A clock that moves only when told to, in either direction: the store clock of an
InMemoryStore or the
client clock of a generator under test.Marks a contract case of an optional capability, such as
seal: it aborts by an assumption on a backend
without the capability, and ContractsRan accepts it skipped.The
RangeStore contract (04-segment.md §1, 06-stores.md §3).The
SlotLeaseStore contract (05-machine-lease.md §2, 06-stores.md §3).Runtimes of every strategy on
InMemoryStores, for the tests of CosId's own integrations and other runtime users.