-
Notifications
You must be signed in to change notification settings - Fork 10
add test levels and frameworks description #181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
add test levels and frameworks description #181
Conversation
The created documentation from the pull request is available at: docu-html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be discussed in https://github.com/orgs/eclipse-score/discussions/407#discussioncomment-14511771
From formal point of you, there is already a concept document, why not add that content in the existing one?
This originated from Monday's alignment meeting where it was suggested that we are missing this kind of information and it is good idea to create it just to be on the same page. I can move/merge if there is a better place. |
|
||
|
||
.. needuml:: | ||
:scale: 50% |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rendered UML diagram doesn't fit on a page. The scale
parameters seems to have no effect, even it is mentioned in sphinx documentation. I would prefer to keep UML code instead of svg graphic above - does anyone know how to fix it?
:need:`wp__verification_feat_int_test` aims to validate that features | ||
work together as intended. This is done by exercising functionality through public APIs and validating feature behavior, | ||
interactions between them and their components. Feature integration tests are automatically executed | ||
on a pull request when a feature is requested to be integrated in SCORE. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Process Description is project independent and tool agnostic, SCORE -> replace with Project
|
||
Existing Verification Frameworks | ||
******************************** | ||
* **ITF (Integration Test Framework):** Allows execution of Feature Integration Tests on target hardware or simulation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are tools, specific programming languages, this content must be moved into PMP section Verification of S-CORE, if is S-CORE specific, compare here https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Splitting and moving parts are the opposite of this task - the goal was to create a single page which gathers those information.
Let me draft this PR for now and clarify with Anton once he is available.
2177fcf
to
1d601d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like only Feature Integration Tests validate something.
What about Component Integration Tests which also verify requirements.
Also, I would assume there will also be InternalClass for Components.
It may need to be made clear that the illustration is incomplete.
The overview may also enhance this page to have it enhanced by verification artifacts: https://eclipse-score.github.io/process_description/main/general_concepts/score_traceability_concept.html
One pager description how we understand different levels of testing in SCORE project and list of current frameworks.