-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Improve error format with errors during setup #717
Labels
good first issue
easy issue that is friendly to new contributor
topic: reporting
related to terminal output and user-facing messages and errors
type: bug
problem that needs to be addressed
Comments
pytestbot
added
type: bug
problem that needs to be addressed
topic: reporting
related to terminal output and user-facing messages and errors
labels
Jun 15, 2015
RonnyPfannschmidt
added
the
good first issue
easy issue that is friendly to new contributor
label
Jul 25, 2015
This was referenced Jul 23, 2016
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Aug 11, 2016
Fixes pytest-dev#717. Follow-up to pytest-dev#1762.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Aug 14, 2016
Fixes pytest-dev#717. Follow-up to pytest-dev#1762.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Aug 14, 2016
Fixes pytest-dev#717. Follow-up to pytest-dev#1762.
blueyed
added a commit
to blueyed/pytest
that referenced
this issue
Aug 14, 2016
Fixes pytest-dev#717. Follow-up to pytest-dev#1762.
This was referenced Aug 19, 2016
This was referenced Nov 11, 2017
Merged
This was referenced Nov 20, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
easy issue that is friendly to new contributor
topic: reporting
related to terminal output and user-facing messages and errors
type: bug
problem that needs to be addressed
Originally reported by: Daniel Hahler (BitBucket: blueyed, GitHub: blueyed)
When there is an error during setup (in case of a missing fixture), the
output is not easily parsable:
It would be nice if the line containing the error ("fixture 'db2' not found")
was prefixed with "E", and maybe the additional information with ">".
I am in the process of improving the errorformat string for Vim, defined/based
on the pytest-vim-compiler
plugin.
The text was updated successfully, but these errors were encountered: