eclipse-score / eclipse-score/baselibs
filesystem: clean up test-to-requirement traceability
- Dominant language
- C++
- Stars
- 26
- Forks
- 85
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 47
Description
Apply the test-to-requirement traceability clean-up described in #522 to the Filesystem component (`score/filesystem/`).
Review every C++ gtest against the current `comp_req__filesystem__...` 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 the traceability clean-up described in #522, then inspect every C++ gtest in score/filesystem/ against the current comp_req__filesystem__... needs. Reconcile requirements and test behavior in both directions, adding the specified metadata only where tests genuinely verify requirements; leave inspection-only requirements without artificial coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100