Fix tests for pytest 3.3 #550
Comments
blueyed
added a commit
to blueyed/pytest-django
that referenced
this issue
Dec 3, 2017
Workaround for pytest-dev#550.
Closed
blueyed
added a commit
to blueyed/pytest-django
that referenced
this issue
Dec 3, 2017
blueyed
added a commit
that referenced
this issue
Dec 3, 2017
timb07
pushed a commit
to timb07/pytest-django
that referenced
this issue
May 26, 2018
beyondgeeks
added a commit
to beyondgeeks/django-pytest
that referenced
this issue
Sep 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some tests are failing because output matching does not take into account the new
console_output_stylefrom pytest 3.3.Should we add
['-o', 'console_output_style', 'cassic']to affected django_testdir.runpytest_subprocess, or rather match it using*at then end?The latter might not be reliable though.
The text was updated successfully, but these errors were encountered: