Skip to content

help the user in the rare case this assertion actually fails #1631

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

Merged
merged 1 commit into from
Jun 21, 2016
Merged

help the user in the rare case this assertion actually fails #1631

merged 1 commit into from
Jun 21, 2016

Conversation

obestwalter
Copy link
Member

Trivial change discussed during the sprint to give the user the name, where the assertion fails.

@coveralls
Copy link

coveralls commented Jun 21, 2016

Coverage Status

Coverage remained the same at 92.205% when pulling 2b5c2f3 on Avira:master into 5d8d1db on pytest-dev:master.

@The-Compiler
Copy link
Member

I don't really get what this is about (sorry 😆), but I think adding a test would be nice if you can easily add one to the existing ones.

@obestwalter
Copy link
Member Author

obestwalter commented Jun 21, 2016

This just came up in the fixture discussion we had. If this assertion ever fails (which is very rare) it will display the name that actually caused the assertion to fail.

@nicoddemus nicoddemus merged commit 61ede09 into pytest-dev:master Jun 21, 2016
RonnyPfannschmidt added a commit that referenced this pull request Jun 22, 2016
Add test for change in pull request #1631
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.

4 participants