You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure to link this issue with the PR for your improvement.
Following improvements in the verification process have been identified during the porting from incubator and adopting to the latest process model structure:
software_verification.rst (Verification Plan as part of PMP):
✔️ Within the coverage of detailed design additional verification measures such as "data flow coverage" should be checked.
✔️ Within the coverage of architectural design additional verification measures such as "sequence diagrams" should be checked. Question is also how to define the coverage of such measures.
Additionally, tools will be provided to automatically generate coverage tests based on the unit source code.
Testing community is not considering a fully automated test case creation anymore.
verification_guidance.rst (Guideline how to perform verification activities)
It is hard to show full coverage of requirements, if everything is hidden in a PR review. A concept like "have a specification which links multiple tests of partially covered type" or similar is needed.
Uh oh!
There was an error while loading. Please reload this page.
Important
Make sure to link this issue with the PR for your improvement.
Following improvements in the verification process have been identified during the porting from incubator and adopting to the latest process model structure:
software_verification.rst (Verification Plan as part of PMP):
✔️ Within the coverage of detailed design additional verification measures such as "data flow coverage" should be checked.
score/docs/platform_management_plan/software_verification.rst
Line 285 in 548fd89
✔️ Within the coverage of architectural design additional verification measures such as "sequence diagrams" should be checked. Question is also how to define the coverage of such measures.
score/docs/platform_management_plan/software_verification.rst
Line 297 in 548fd89
verification_getstrt.rst (Verification Getting Started)
score/docs/process/process_areas/verification/verification_getstrt.rst
Line 64 in 548fd89
Testing community is not considering a fully automated test case creation anymore.
verification_guidance.rst (Guideline how to perform verification activities)
It is hard to show full coverage of requirements, if everything is hidden in a PR review. A concept like "have a specification which links multiple tests of partially covered type" or similar is needed.
score/docs/process/process_areas/verification/guidance/verification_guidance.rst
Lines 81 to 85 in 548fd89
✔️ This is handled by the new test level assignment where a unit test can also link to a component requirement
❌ How to execute manual test locally, and report execution results need to be described.
Follow up in Bugfix: Practical execution of verificaiton activities #1091
❌ How to execute automated test cases locally (e.g. before creation of a PR) need to be described
score/docs/process/process_areas/verification/guidance/verification_guidance.rst
Line 89 in 548fd89
Follow up in Bugfix: Practical execution of verificaiton activities #1091
Verification methods and types need to be described in more detail:
score/docs/process/process_areas/verification/guidance/verification_guidance.rst
Line 133 in 548fd89
Follow up in Bugfix: Practical execution of verificaiton activities #1091
verification_process_toolreqs.rst (Verification requirements put to tooling)
score/docs/process/process_areas/verification/guidance/verification_process_toolreqs.rst
Line 144 in 548fd89
TODOs kept in source code:
❌ Requires implementation of #599:
score/docs/process/process_areas/verification/verification_concept.rst
Line 153 in 548fd89
✔️ Requires merge of PR #526:
score/docs/process/process_areas/verification/workflows.rst
Line 31 in 548fd89
score/docs/process/process_areas/verification/workproducts.rst
Line 132 in 548fd89
TODOs from #441 comments:
process: initial documentation of verification #441 (comment)
process: initial documentation of verification #441 (comment)
process: initial documentation of verification #441 (comment)
process: initial documentation of verification #441 (comment)
and process: initial documentation of verification #441 (comment)
The text was updated successfully, but these errors were encountered: