Repository navigation
"RecordProperties" in baselibs not properly used #62
Description
According to the process_description verification templates the following properties should be used to indicate trace to requirements:
RecordProperty("PartiallyVerifies", "ID_2, ID_3, ...");
RecordProperty("FullyVerifies", "ID_4, ID_5, ...");
The mentioned IDs are requirement IDs from feature and component requirements. It is also possible to link to the component architecture.
This can be found in the general traceability concept
Within baselibs the test cases link to requirements via verifies which is not correct. Additionally, they link to artifacts which are not part of the S-CORE language. Examples of wrong usage are:
RecordProperty("Verifies", "SCR-46010294");
::testing::Test::RecordProperty("Verifies", "::score::utils::EncodeBase64()")
this->RecordProperty("Verifies", "5310867");
In total this affects around 60 files within baselibs with many mentions. Details can be found here: https://github.com/search?q=repo%3Aeclipse-score%2Fbaselibs+RecordProperty%28%22Verifies%22&type=code
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
- Status
Activity
MaximilianSoerenPollak commentedon Feb 25, 2026
I am currently working on a feature to enable 'non compliant' use so to speak.
With this docs-as-code will no longer throw an error if there are too many properties as well as when there are not all properties needed to make a Testlink.
It will inform and skip those tests (to link)
eclipse-score/docs-as-code#413 to track progress.
4og commentedon Aug 26, 2026
All requirement tracing will be revised in #522