Use this checklist to run a fast, repeatable technical review.
Run:
make clean
make all
make test-unit
make ci-checkExpected:
- Build succeeds with no compiler warnings promoted to errors.
- Unit tests pass.
cppcheck,clang-tidy, layering checks, and sanitizer-enabled debug build pass.
Run:
./build/testrig --run-all --json > /tmp/testrig_review.json
./build/testrig --run-all --json > /tmp/testrig_review_2.json
cmp /tmp/testrig_review.json /tmp/testrig_review_2.jsonExpected:
cmpreports no differences.- JSON contains
schema_version,software_version,requirement_id, andsummary.
Run malformed-input checks:
printf 'TICK 1 RPM nan TEMP 80 OIL 3 RUN 1\n' > /tmp/bad_nan.txt
./build/testrig --script /tmp/bad_nan.txt --strict
printf 'TICK 2 RPM 2200 TEMP 80 OIL 3 RUN 1\nTICK 1 RPM 2300 TEMP 81 OIL 3 RUN 1\n' > /tmp/bad_tick_order.txt
./build/testrig --script /tmp/bad_tick_order.txt --strictExpected:
- Non-zero exit code for malformed inputs.
- Clear parse failure message.
Inspect:
docs/requirements_traceability_matrix.md- JSON output from
--run-all --json
Expected:
- Scenario names map to requirement IDs in the matrix.
- JSON
requirement_idvalues are present and consistent with matrix intent.
Inspect headers:
include/engine.hinclude/hal.hinclude/script_parser.hinclude/test_runner.h
Expected:
_Static_assertchecks compile successfully.- Public APIs document preconditions and postconditions.