New issue 438: entering pdb from pytest's internal test suite breaks pytest
later
https://bitbucket.org/hpk42/pytest/issue/438/entering-pdb-from-pytests-internal-test
Jurko Gospodnetić:
Consider the following test case prepared to be run as a part of pytest's
internal test suite:
```
class Tes
New issue 439: capsys fixture does not collect the same test output as reported
by pytest
https://bitbucket.org/hpk42/pytest/issue/439/capsys-fixture-does-not-collect-the-same
Jurko Gospodnetić:
I noticed that test fixture output gets reported by pytest as part of the
output captured for a part
New issue 440: parametrized fixture output captured inconsistently
https://bitbucket.org/hpk42/pytest/issue/440/parametrized-fixture-output-captured
Jurko Gospodnetić:
When using parametrized module scoped fixtures, their finalization output gets
captured inconsistently. It does not get captured
New issue 441: parametrized fixture + module scope + failing test + '-x' option
= invalid fixture finalizer output
https://bitbucket.org/hpk42/pytest/issue/441/parametrized-fixture-module-scope-failing
Jurko Gospodnetić:
The following test demonstrates the issue. You can run it as a part of the
New issue 442: Make reported captured output include function scope fixture
finalizer output.
https://bitbucket.org/hpk42/pytest/issue/442/make-reported-captured-output-include
Jurko Gospodnetić:
My suggestion is to make regular test output capture include output from
function scoped fixture fi
