Skip to content

Conversation

@cdecker
Copy link
Member

@cdecker cdecker commented Jan 20, 2026

Our internal QA team would like to have the ability of linking directly to a run from the test report, so here we just add any envvar that might be of interest for cross-linking.

@cdecker cdecker force-pushed the 2026w03-pytest-runid branch from 51c519c to 2827e16 Compare January 20, 2026 15:25
Changelog-None: Not user visible
@cdecker cdecker force-pushed the 2026w03-pytest-runid branch from 2827e16 to f6a7aa3 Compare January 21, 2026 10:34
The fixture was defined in fixtures.py but not imported by any test configuration, preventing it from running. Explicitly importing it in tests/conftest.py ensures it is registered and the environment variables are added to the report.
The log_global_env_facts fixture records GitHub Actions environment
variables (including GITHUB_RUN_ID) into the JUnit XML report properties.

Previously this fixture was defined in tests/fixtures.py but wasn't
being executed. Moving it to the root conftest.py ensures it runs
automatically for all test sessions.

This fixes the issue where pytest reports uploaded as CI artifacts
were missing the GitHub run metadata.
Add required second blank line after fixture definition.
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.

2 participants