test: standardise pytest config and remove -m filter from CI#277
Merged
test: standardise pytest config and remove -m filter from CI#277
Conversation
- Remove broken '-m not integration' from addopts; integration tests already use @pytest.mark.skipif(not GITHUB_TOKEN) so they skip automatically in CI without a filter - Replace flaky marker with e2e marker - Remove -m "not integration" from CI test command; use --junitxml for consistent test-results output
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
'-m not integration'fromaddopts; integration tests already use@pytest.mark.skipif(not GITHUB_TOKEN, ...)so they skip automatically in CI without needing a-mfilterflakymarker withe2emarker (consistent with other repos)-m "not integration"from CI test command; simplify to--junitxml=build/junit.xmlfor consistent JUnit outputTest plan