Add documentation for testing guidelines#2554
Add documentation for testing guidelines#2554Rahul-Sutariya wants to merge 1 commit intoeclipse-score:mainfrom
Conversation
|
|
ca6f555 to
aa20c46
Compare
|
The created documentation from the pull request is available at: docu-html |
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
|
@Rahul-Sutariya I agree to the previous comments we should align here as there is already some duplication to the existing process and guidelines. Merging yours into what exists will be best. Let us align (responded to you on slack already) and see how things will fit best. |
pahmann
left a comment
There was a problem hiding this comment.
Need to be integrated into Verification plan as part of PMP and the verification section in process description.
- Given When Then is already there.
- Templates are there.
- Existing documents will benefit from the best practices described
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.