eclipse-score / eclipse-score/time
Establish Unit Test Metadata (Traceability)
- Dominant language
- C++
- Stars
- 2
- Forks
- 12
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 24
Description
### What
Tests exist for all components but none carry the process-required GTest
`RecordProperty` metadata (`TestType`, `DerivationTechnique`, `Description` in
Given-When-Then format, `FullyVerifies` / `PartiallyVerifies` linking to `comp_req`
UIDs). Without this metadata, the process-mandated verification report cannot be
generated.
### References
- [S-CORE Verification](https://eclipse-score.github.io/process_description/main/process_areas/verification/)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by inventorying the existing component tests and reading the linked S-CORE Verification guidance for the required GTest RecordProperty fields. Add TestType, DerivationTechnique, Given-When-Then Description, and FullyVerifies or PartiallyVerifies links to comp_req UIDs. Done means all component tests carry the metadata needed to generate the verification report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100