Skip to content

Conversation

PiotrKorkus
Copy link
Contributor

One pager description how we understand different levels of testing in SCORE project and list of current frameworks.

Copy link

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@masc2023 masc2023 left a 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?

@PiotrKorkus
Copy link
Contributor Author

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%
Copy link
Contributor Author

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.
Copy link
Contributor

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.
Copy link
Contributor

@masc2023 masc2023 Sep 26, 2025

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

Copy link
Contributor Author

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.

@PiotrKorkus PiotrKorkus force-pushed the piotrkorkus_test_frameworks branch from 2177fcf to 1d601d2 Compare September 30, 2025 10:23
@PiotrKorkus PiotrKorkus marked this pull request as draft September 30, 2025 10:23
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants