pytest-dev / pytest-dev/pytest
followup for partial outcome matching
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.5k
- Forks
- 3.4k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 35
Description
in #9475 we loosened the matching for outcomes to resolve #9471
in order to resolve the details we ought to determine a way to match outcomes exactly
a discussion on outcomes and their counting/different ways to count them to make sense of test runs ill have to happen
part of that discussion can be expectations for "optional" and "external" outcomes
for example the outcomes coming in by pytest-manual-marker or pytest-external-blocker
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issues #9475 and #9471 to understand the existing outcome-matching change and the problem it addressed. Then examine how outcomes from pytest-manual-marker and pytest-external-blocker should be matched and counted, including expectations for optional and external outcomes; done requires an agreed exact-matching approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100