-
Notifications
You must be signed in to change notification settings - Fork 73
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
Keep consistency in the output #173
Comments
Just for reference: pytest should also be able to run tests via
Do you mean a custom hint, which fails because it cannot include the space?
I'd prefer Would Anyway, in general this repo appears to be quite inactive currently, and CI would fail for your PR anyway, but feel free to give it a try already! This is something that annoyed me also about pytest-sugar (I am not using it currently), and thought I had done some PR in this regard myself, but could not find it. Check out #172 also. |
There is some discussion / brainstorming with regard to this in pytest itself: pytest-dev/pytest#5002 (comment). |
In my use cases I usually just want to jump into the file rather than running it again with pytest so the line number next to the filename is really handy (at least iTerm2 allows direct jump with the line number) |
Related: pytest-dev/pytest#5241 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
OK, thanks for the clarification. |
Right now, when a test fails the output looks like this:
The way the failing test (ie
PATH:LINE TEST
) is displayed is not the natural way pytest displays test paths (iePATH::TEST
), and I think it is unpractical for some reasons:A more practical way to display the report would be to keep the test path the way pytest use them. For example what do you think of this output?
If you agree, I am willing to make a pull request. What do you think?
Cheers
The text was updated successfully, but these errors were encountered: