-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
good first issueeasy issue that is friendly to new contributoreasy issue that is friendly to new contributortopic: reportingrelated to terminal output and user-facing messages and errorsrelated to terminal output and user-facing messages and errorstype: bugproblem that needs to be addressedproblem that needs to be addressed
Description
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.
Metadata
Metadata
Assignees
Labels
good first issueeasy issue that is friendly to new contributoreasy issue that is friendly to new contributortopic: reportingrelated to terminal output and user-facing messages and errorsrelated to terminal output and user-facing messages and errorstype: bugproblem that needs to be addressedproblem that needs to be addressed