Skip to content
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

A commandline flag to override pytrace in failure #6651

Open
FortStatement opened this issue Feb 1, 2020 · 0 comments
Open

A commandline flag to override pytrace in failure #6651

FortStatement opened this issue Feb 1, 2020 · 0 comments
Labels
topic: reporting related to terminal output and user-facing messages and errors type: enhancement new feature or API change, should be merged into features branch

Comments

@FortStatement
Copy link

I use pytest to automatically check my students' exercises.
They receive the output from pytest.fail, and I don't want them seeing the entire stack trace, including local paths, potential edge cases they're supposed to find themselves, et cetera.
Currently, all my tests use pytest.fail(..., pytrace=False), but this is far from ideal, as I have many assistants writing tests and not all of them are familiar with this necessity.

I made a fork that adds the --no-trace flag, opening the issue to submit a pull request.

@blueyed blueyed added topic: reporting related to terminal output and user-facing messages and errors type: enhancement new feature or API change, should be merged into features branch labels Feb 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: reporting related to terminal output and user-facing messages and errors type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Development

No branches or pull requests

2 participants