Expand description
Mock plugins for tests.
The mocks accept every peer and simulate a handshake in exactly two steps. Never for production — they provide no real crypto.
Purpose:
- Validate the SPI interface against an actually working flow (signature checks, handshake state machine).
- From v1.4 on the DCPS layer can sub-test against the mock before the production plugin is finished.
zerodds-lint: allow no_dyn_in_safe
(tests instantiate Box<dyn AuthenticationPlugin>.)
Structs§
- Mock
Access Control Plugin - Mock access control: allows everything. Tests only.
- Mock
Authentication Plugin - Mock implementation — accepts everything, handshake step count hard-coded.
- Mock
Data Tagging Plugin - Mock DataTagging plugin: stores tag lists per endpoint GUID in an in-memory map. Returns an empty Vec for an unknown GUID (spec-compliant default).
- Mock
LogEntry - A log entry — collected for test assertions.
- Mock
Logging Plugin - Mock logger: collects all events in a
MockLogSinkso tests can inspect the events afterwards.
Type Aliases§
- Mock
LogSink - Shared sink type —
Arc<Mutex<Vec<MockLogEntry>>>.