Skip to content

followup for partial outcome matching #9543

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

Open
RonnyPfannschmidt opened this issue Jan 25, 2022 · 0 comments
Open

followup for partial outcome matching #9543

RonnyPfannschmidt opened this issue Jan 25, 2022 · 0 comments
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@RonnyPfannschmidt
Copy link
Member

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

@Zac-HD Zac-HD added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Development

No branches or pull requests

2 participants