CANopen device-driver codegen — verification

Test cases verifying the CANopen device-driver codegen toolchain. Each test directive :verifies: one or more requirements from CANopen device-driver codegen (or building blocks / quality goals from CANopen device-driver codegen — architecture (arc42)).

The toolchain is build-time only — there are no cyclic-runtime integration tests beyond what Connector framework — verification already covers for CAN (SocketCAN) reference c... (FEAT_0046). The verification surface here is therefore heavier on snapshot / golden-file / property tests than on multi-process integration. Mirrors the structure of Device-driver codegen — verification so reviewers can read both verification pages 1:1.

The test cases are grouped by area (see the toctree): the eight crate-layer areas mirroring the requirement feats — OD-core unit tests, EDS parser tests, codegen / IR tests, taktora backend snapshot tests, runtime trait surface tests, build helper tests, CLI tests, and verifier tests — and a final cross-cutting page carrying the reproducibility and traceability checks.

• OD-core unit tests
• EDS parser tests
• Codegen / IR tests
• taktora backend snapshot tests
• Runtime trait surface tests
• Build helper tests
• CLI tests
• Verifier tests
• Cross-cutting tests
  • Cross-cutting reproducibility tests
  • Cross-cutting traceability

On this page

• CANopen device-driver codegen — verification