test: maximize FuSa/cyber requirement test coverage to 100%#19
Merged
Conversation
Raise requirement->test traceability from 51% (166/322) to 100% (331/331). - Add REQ-CLI-001..004 and REQ-RELAY-001..005 to .fusa-reqs.json (were tested but undeclared); fix test_cli/test_relay to use fusa:test. - Bucket A: complete fusa:test headers + add real cases for previously untested reqs across admin, authz, capi, config, dyndata, federation, firmware, observe, proxy, record, redundancy, zonegroup (thread-safety, error/counter capture, ErrClosed/ErrTimeout failover, latency-budget timeout, multi-chunk transfer, value semantics, context-deadline). - Bucket B: add 13 new test files (canbr, ddsbr, doipbr, grpcbridge, linbr, mqttbr, restbridge, someipbr, udsbr, tsn, mdns, powerstate, tls) and wire into CTest. Stub/TLS tests assert the observable surface (function_not_supported, config defaults, secure-by-default refusal). Full suite: 41 ctest suites, 323 TEST_CASEs. All security controls (AUTH, TLS, E2E, CAPI) test-traced. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Matt Jones <47545907+SoundMatt@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Raises requirement→test traceability from 51% (166/322) to 100% (331/331), across both functional-safety (ISO 26262) and cybersecurity (IEC 62443 / mTLS / E2E) requirements.
Changes
.fusa-reqs.json— they were exercised by tests but absent from the DB. Fixedtest_cli/test_relayto use thefusa:testtag (they usedfusa:req, which made them invisible to the coverage scan).fusa:testheaders and added real cases for previously-untested requirements — thread-safety (admin/authz/dyndata/observe/record), span error + counter capture (observe), ErrClosed/ErrTimeout failover (redundancy), latency-budget timeout & deregister-closes-upstream (proxy), multi-chunk firmware transfer, federation close/closed-lookup/dup-register, config ParseError, zonegroup value-semantics & context-deadline.Verification
rcp_latencyis a pre-existing timing flake under parallel load; passes in isolation and CI runs serially.)Note:
TARA.mdworking-tree change is the parked case-collision item and is intentionally excluded from this PR.