pytest evaluation

[alekseyborisyukvalidas]

Added tool evaluation for pytest
1 use case: Run tests and generate test report
added safety measures where availbale

[github-actions]

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

[MaximilianSoerenPollak]

We are also using pytest (but also other test frameworks) to facilitate the traceability to tests.
I'm unsure if this has / should play into here.

[alekseyborisyukvalidas]

We are also using pytest (but also other test frameworks) to facilitate the traceability to tests. I'm unsure if this has / should play into here.

@MaximilianSoerenPollak, if you could give me the list of these frameworks and where/how they used, i can extend the existing tool list

[AlexanderLanin]

does this say "yes" to there is an impact on detection or there is a detection? Where can I find the detection? Is "Check test run status" the entire detection description? Unfortunately, I have no idea what that means

[alekseyborisyukvalidas]

This "yes" is to "Impact safety detection sufficient?"

[alekseyborisyukvalidas]

Pytest is only part of ITF and not supposed to used independently according to: https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html

[MaximilianSoerenPollak]

Pytest is only part of ITF and not supposed to used independently according to: https://eclipse-score.github.io/score/main/platform_management_plan/software_verification.html

Many repositories use it themselfs see here:

https://github.com/eclipse-score/docs-as-code/blob/main/src/extensions/score_source_code_linker/tests/
https://github.com/eclipse-score/persistency/tree/main/tests/test_cases/tests

Etc.

So if this is truly the case, then these all need to be updated & changed.
I was not aware of such restriction.

@AlexanderLanin does this ring a bell for you?
Not sure who else to tag / ask here.