Adds record_property in tests for req traceability - #276
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
fb186c0 to
b0bfd32
Compare
b0bfd32 to
a3780a2
Compare
|
The created documentation from the pull request is available at: docu-html |
a3780a2 to
86c4f51
Compare
|
I pinged @PiotrKorkus as he is testing lead, he will have a look |
| :derived_from: feat_req__logging__compat_dlt, feat_req__logging__log_sinks_network | ||
| :status: valid | ||
| :satisfied_by: comp__datarouter | ||
| :testlink: https://github.com/eclipse-score/logging/blob/main/score/datarouter/test/ut/ut_logging/test_dltserver.cpp#L150 |
There was a problem hiding this comment.
testlinks have to be autogenerated from .xml test reports based on properties filled in test
https://eclipse-score.github.io/process_description//main/process_areas/verification/guidance/verification_templates.html
There was a problem hiding this comment.
Hi @PiotrKorkus Since we have not entirely migrated to score and still relying on the exports from internal base, we cannot make changes to the sources here. In that regard, the test links here are references for later adaptations. I can create a follow-up task to track that. Works for you?
There was a problem hiding this comment.
this testlink is not valid as it doesnt bring all the information about pass/fail from the test. I dont see any benefit of having such a placeholder.
There was a problem hiding this comment.
Thanks for the feedback
There was a problem hiding this comment.
@PiotrKorkus i see the build docs actually generates the stats from the test artifacts. I will wire it to what has already been linked to so that we do not lose that trace.
86c4f51 to
8b2686d
Compare
8b2686d to
1fb471f
Compare
1fb471f to
638fffa
Compare
638fffa to
8b43521
Compare
| RecordProperty("FullyVerifies", "comp_req__data_router__dlt_multiple_channels"); | ||
| RecordProperty("Description", "Check that a DLT log channel can be constructed with default parameters."); | ||
| RecordProperty("TestType", "requirements-based"); | ||
| RecordProperty("DerivationTechnique", "requirements-analysis"); |
There was a problem hiding this comment.
Component requirements should be verified by Component Integration Tests not Unit Tests
There was a problem hiding this comment.
true a unit does not cover it entirely, thanks
| TOTAL_NONVERBOSE_MESSAGES = 11 | ||
|
|
||
|
|
||
| def test_datarouter_filters(target, datarouter_on_target, dlt_capture): |
There was a problem hiding this comment.
In Python we should use decorator according to the process https://eclipse-score.github.io/process_description//main/process_areas/verification/guidance/verification_templates.html#python-properties-template
There is ITF plugin for that: https://github.com/eclipse-score/itf/blob/1ce9b563e4a6f6b648ca313967fb2beb10f00317/score/itf/plugins/BUILD#L125-L132
9ce3033 to
eef4334
Compare
eef4334 to
73405ee
Compare
- Helps identifying gaps in the module - Extend to inlcude all deps after other repos have fixed covrage as well
- for traceability of requirements
73405ee to
f5c57fa
Compare
Notes for Reviewer
Stats updated based on the links: https://eclipse-score.github.io/logging/pr-276/verification_report/stats.html
NOTE: We still need to cleanup the existing entries (legacy since those were from an internal codebase), but that will be part of the future release after we migrate entirely to score.
Pre-Review Checklist for the PR Author
Checklist for the PR Reviewer
Post-review Checklist for the PR Author
References
Closes #