-
Notifications
You must be signed in to change notification settings - Fork 22
Fixing pytest decorator usage #217
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?
Fixing pytest decorator usage #217
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
|
|
||
| import pytest | ||
| from testing_utils import LogContainer, ScenarioResult | ||
| from attribute_plugin import add_test_properties |
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.
Could you add this file https://github.com/eclipse-score/reference_integration/blob/main/feature_integration_tests/test_cases/test_properties.py and decorator via it?
This will allow non-bazel execution
tests/python_test_cases/pytest.ini
Outdated
| env = D:RUST_BACKTRACE = 1 | ||
| junit_family = xunit1 | ||
| filterwarnings = | ||
| error |
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.
I think this one is too general and shouldnt be added
| @@ -0,0 +1,22 @@ | |||
| # ******************************************************************************* | |||
| # Copyright (c) 2026 Contributors to the Eclipse Foundation | |||
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.
current version of tooling fails with 2026, it needs to be 2025
Already fixed with updated cr_checker version but it would need to be released to registry first and bumped here
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.
We should bump that then no? Or will this make even more issues?

Exchanging pytest marks to pytest decorator for XML attributes.
This PR needs this PR in docs as code to be merged & a new release of Docs-as-code first=> eclipse-score/docs-as-code#347