# Test Fixtures

These are small, made-up inputs for checking both success and failure paths.
They are not copied from a vehicle database.

- `template_valid_sanitized.dbc` should pass.
- `template_invalid_semantic_sanitized.dbc` should fail semantic validation.
- `template_roundtrip_mismatch_sanitized.dbc` is paired with intentionally
  inconsistent C code in `roundtrip_mismatch_artifacts/`.
- `template_broken_parser_demo.c` is intentionally invalid C.

Quick checks from the repository root:

```bash
specgo ing tests/template_valid_sanitized.dbc -f
specgo val specgo_output/output/template_valid_sanitized.ir.yaml

specgo ing tests/template_invalid_semantic_sanitized.dbc -f
specgo val specgo_output/output/template_invalid_semantic_sanitized.ir.yaml

specgo ing tests/template_roundtrip_mismatch_sanitized.dbc -f
specgo val specgo_output/output/template_roundtrip_mismatch_sanitized.ir.yaml
specgo rt \
  -i specgo_output/output/template_roundtrip_mismatch_sanitized.ir.yaml \
  -a tests/roundtrip_mismatch_artifacts \
  -n 1 -c 2 --stop-on-fail
```

Generated reports are not committed because they can contain local paths.
