Add documentation for testing guidelines #2554
Conversation
|
|
Rahul-Sutariya
force-pushed
the
rs_testing_guidelines
branch
from
ca6f555 to
aa20c46
Compare
|
The created documentation from the pull request is available at: docu-html |
PiotrKorkus
left a comment
PiotrKorkus
left a comment
There was a problem hiding this comment.
This document is quite specific and oriented only for C++ tests implementation. I find score repo a place for general rules so it shouldn't be too strict.
Other languages are omitted and they have their own rules. How about a general Guideline and then C++/Rust/Python specific ones?
Also some parts of this document are already mentioned in process description - did you check them?
e.g.:
- https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html
- https://eclipse-score.github.io/process_description/main/process_areas/verification/guidance/verification_specification.html
Those should be in harmony, not repeat or conflict with each other.
| :security: YES | ||
| :realizes: wp__sw_development_plan | ||
|
|
||
| These guidelines are based on discussions within the score com team. They're not set in stone and can be changed in the future. |
There was a problem hiding this comment.
If that's specific to communication, maybe it should be a part of com specific documentaiton
| :status: valid | ||
| :safety: ASIL_B | ||
| :security: YES | ||
| :realizes: wp__sw_development_plan |
There was a problem hiding this comment.
This work product is already here, https://eclipse-score.github.io/score/main/platform_management_plan/software_development.html, you may add more content to that here, our Verification Plan https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html, so get in touch with @pahmann , where these content fits best
3 participants
This pull request adds documentation for testing guidelines to the SCORE repository. It introduces a new set of written instructions and best practices on how to write, organize, and run tests for the project. These guidelines aim to help contributors and maintainers consistently implement high-quality tests across the codebase. The PR includes documentation files and updates relevant to the project’s docs-as-code framework.