Skip to content

fix: validate marker loop_scope values - #1586

Closed
ketpatil77 wants to merge 1 commit into
pytest-dev:mainfrom
ketpatil77:fix-invalid-loop-scope
Closed

ketpatil77 wants to merge 1 commit into
pytest-dev:mainfrom
ketpatil77:fix-invalid-loop-scope

Conversation

@ketpatil77

Copy link
Copy Markdown

Fixes #1584. Reuse the existing scope validator for asyncio marker loop_scope values instead of a bare assert, producing the documented usage error for invalid scopes.

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.89%. Comparing base (93893ec) to head (b150b19).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1586      +/-   ##
==========================================
+ Coverage   94.50%   94.89%   +0.38%     
==========================================
  Files           2        2              
  Lines         510      509       -1     
  Branches       62       61       -1     
==========================================
+ Hits          482      483       +1     
+ Misses         22       21       -1     
+ Partials        6        5       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tjkuson

tjkuson commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Thank you for attempting to contribute, but there's already a PR open for this issue that seems closer to completion.

Also, please keep in mind the AI policy when contributing to this project.

@tjkuson tjkuson closed this Oct 21, 2026
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.

Invalid loop_scope in the asyncio marker raises AssertionError instead of a usage error

3 participants