eclipse-score / eclipse-score/baselibs

result: clean up test-to-requirement traceability

Open
#554 0 comments 0 reactions 0 assignees View on GitHub
comp-result
Dominant language
C++
Stars
26
Forks
85
Avg merge
2d 15h
Merged PRs (30d)
46

Description

Apply the test-to-requirement traceability clean-up described in #522 to the Result component (`score/result/`).

Review every C++ gtest against the current `comp_req__result__...` needs. Add mandated `FullyVerifies` or `PartiallyVerifies` links, `TestType`, `DerivationTechnique`, and self-contained `Description` metadata where a test genuinely verifies a requirement. Reconcile requirement text and test behavior in both directions, and leave non-functional requirements that are verifiable only by inspection without artificial test coverage.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with issue #522 and inspect the C++ gtests under score/result/ alongside the current comp_req__result__... requirements. Map each genuine verification to the required metadata, reconcile requirement text with test behavior in both directions, and leave inspection-only requirements without artificial tests. Done means the Result traceability metadata is complete and consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.