Color highlight on the name of the failed tests #1
Conversation
This file contains 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
|
|
|
Cool Ogro! Would you mind opening this PR at pytestdev/pytest instead though? This is just a fork. 😄 |
|
Absolutely. I just wanted to run this through you before sending the PR there. |
nicoddemus
pushed a commit
that referenced
this pull request
Jun 26, 2016
Factor setuponly code out of runtestprotocol().
nicoddemus
added a commit
that referenced
this pull request
Nov 9, 2016
nicoddemus
added a commit
that referenced
this pull request
Nov 9, 2016
nicoddemus
pushed a commit
that referenced
this pull request
Feb 22, 2019
update links for virtualenv -> venv
nicoddemus
pushed a commit
that referenced
this pull request
Jun 29, 2023
Updated logging.py for pytest-dev#9146
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm proposing this small enhancement because it is sometimes difficult, especially when using verbose tests output, to immediately spot which tests are failing in the middle of all the tracebacks and other output messages. I believe by highlighting the separator line containing the test name which is failing in red would allow developers to quickly spot the failed test and target where his next action should be.