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

Improve error format with errors during setup #717

Closed
pytestbot opened this issue Apr 12, 2015 · 0 comments
Closed

Improve error format with errors during setup #717

pytestbot opened this issue Apr 12, 2015 · 0 comments
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
Copy link
Contributor

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:

_____________ ERROR at setup of test_foo ______________
file …/project/app/test_models.py, line 334
  def test_foo(db2):
        fixture 'db2' not found
        available fixtures: _django_clear_outbox, ...
        use 'py.test --fixtures [testpath]' for help on them.

…/project/app/test_models.py:334

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.


@pytestbot 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 RonnyPfannschmidt added the good first issue easy issue that is friendly to new contributor label Jul 25, 2015
blueyed added a commit to blueyed/pytest that referenced this issue Aug 11, 2016
blueyed added a commit to blueyed/pytest that referenced this issue Aug 14, 2016
blueyed added a commit to blueyed/pytest that referenced this issue Aug 14, 2016
blueyed added a commit to blueyed/pytest that referenced this issue Aug 14, 2016
This was referenced Nov 11, 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
Projects
None yet
Development

No branches or pull requests

2 participants