-
Notifications
You must be signed in to change notification settings - Fork 11
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
patch(integration_test_charm.yaml): Add Allure "unknown" status for tests with missing results #183
Conversation
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.
This is massive and long waited. Tnx!
tested again with rebase on #179 on https://github.com/carlcsaposs-canonical/mysql-router-k8s-operator/actions/runs/9415095490/job/25935868156 (to test that if job is cancelled, that completed tests are reported as passed & only non-completed tests are cancelled) |
Opened upstream (allure-pytest) feature request: allure-framework/allure-python#821 to replace our custom pytest plugin |
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.
nice!
…docs Follow up to #183
Generate default results with "unknown" status for every test so that if Allure report is missing (because runner set up failed or integration tests timed out) that those tests show up as "unknown" instead of being omitted from Allure report
Breaking change for Allure users (Allure is in beta & not part of public interface, hence
patch
PR prefix instead ofbreaking
):allure-pytest-collection-report
plugin now required, see .github/workflows/integration_test_charm_allure_beta.md