Add tracebacks and output for xfail and xpass with -rxX option by okken · Pull Request #11735 · pytest-dev/pytest (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation2 Commits5 Checks0 Files changed

Conversation

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

[ Show hidden characters]({{ revealButtonHref }})

okken

This is builds off of @sturmf #11574 which closes #11233

I tried to push changes to Fabian's branch and I think I totally mucked it up.
So I'm starting fresh.

Changs over Fabian's work:

I think that's it.

@okken

@okken okken changed the titlebuilding on 11574: summary changes + testing for xfail and xpass building on 11574: Add summary for xfails with -rxX option

Dec 23, 2023

@okken

@okken okken changed the titlebuilding on 11574: Add summary for xfails with -rxX option WIP: building on 11574: Add summary for xfails with -rxX option

Dec 23, 2023

@okken okken changed the titleWIP: building on 11574: Add summary for xfails with -rxX option building on 11574: Add summary for xfails with -rxX option

Dec 26, 2023

@okken okken mentioned this pull request

Dec 27, 2023

@okken

I backed out "adding assert failure" to xfail summary, as it broke [NOTRUN] behavior for xfail in test_skipping.py and I couldn't figure out how to get around that.

However, running with --tb=line (or really anything more than --tb=no) is a sufficient workaround

@okken okken changed the titlebuilding on 11574: Add summary for xfails with -rxX option Add tracebacks and output for xfail and xpass with -rxX option

Dec 27, 2023

@okken okken mentioned this pull request

Dec 27, 2023

@okken

All of these changes have been merged to #11574

1 participant

@okken