[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

[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.

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.

[anmittag]

@alekseyborisyukvalidas any update on this PR? Otherwise we shall close it by August, 31st

[alekseyborisyukvalidas]

Talked with @PiotrKorkus.
Some components use raw pytest for CIT (e.g. https://github.com/eclipse-score/kyron/blob/main/tests/test_cases/BUILD).

Pytest should be added to evaluation report.
Qualification (if needed) can be combined with ITF (tcl:LOW).

[github-actions]

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

[alekseyborisyukvalidas]

@anmittag, the PR is ready to be merged.

[anmittag]

@alekseyborisyukvalidas please update your PR or close it

[alekseyborisyukvalidas]

It was updated in 36a7272

[masc2023]

@alekseyborisyukvalidas please update your PR or close it

@anmittag, @AlexanderLanin please review again, if your comments have been resolved

[masc2023]

@MaximilianSoerenPollak , @AlexanderLanin , doc build is failing, due to wrong version format, I think we may have now here a conflict, the attribute version was here to indicate the tools version, before we introduced the versioning scheme, can you please check and propose a solution, thank you

[MaximilianSoerenPollak]

this should just be tool_version for the version of the tool.

The version is for the need itself.

[alekseyborisyukvalidas]

Updated in 27fc44d

[github-actions]

Documentation preview for this pull request is available at:
pr-2717: https://eclipse-score.github.io/score/pr-2717/