Thanks a lot for this plugin! It probably saved me countless hours of waiting for my testsuite to finish 🙂

I assume most testsuites with pytest-instafail installed will always want to enable it. This can be done with addopts = --instafail in a pytest.ini.

However, at that point the pytest-instafail plugin needs to be installed for the tests to work at all, which is a bit unfortunate. What do you think about enabling it when installed by default, similar to what e.g. pytest-sugar does? That would avoid this issue, and it's still possible to disable it using pytest's -p no:instafail.

I have pytest.ini with addopts = --instafail.
I have other python program which must collect list of tests. Simple solution here.
To disable pytest output I use argument -p no:terminal as suggested above.
The result is AttributeError: 'NoneType' object has no attribute 'config'
This happens because there is no terminalreporter plugin and None is returned here

In looking at compatibility between instafail 0.2.0 and py.test 2.6.0, it seems like the former is not compatible with the latter. I get 24 test failures against Python 2.7 and 33 failures when running against Python 3.4 when running tox.

please consider moving this nice plugin under pytest-dev organization
http://pytest.org/latest/contributing.html

http://pythonwheels.com/

Right now, only the tar.gz file is being distributed on PyPI for pytest-instafail, which isn't that much of an issue, but it does add some time to installing the package.

This package should be compatible with the Wheel format, considering it doesn't appear to have any C dependencies and it is compatible with both Python 2 and 3. As a result, you should only need to generate a universal wheel and then everyone (on all systems) will get the ability to install pytest-instafail with just the wheel, without having to do any extra work.

Hi!

As per pytest-dev/pytest-xdist#541, pytest-xdist 2.0 will remove the deprecated "slave"
aliases, which have been replaced by "worker" since pytest-xdist 1.22.

To avoid breakage, the team suggests to update your package to use the new terms, and make a new release to avoid sudden breakages once pytest-xdist 2.0 is released.

cc @Zac-HD @RonnyPfannschmidt

Thanks!

Failed: nomatch: 'ERROR collecting test_collect_error.py'
Full build log: instafail.txt

Would it be possible to cut a new release please?
I am still seeing the PytestDeprecationWarnings that have been fixed in #26.

Thanks!

When not in verbose mode, pytest shows each test as a single dot, and shows the percentage completed at the end of the line.

If the line of dots is cut short by instafail, the percentage is not known.

If that happens a few times, it can be hard to gauge whether the test run is nearing completion.

passing --instafail=andlatefail to show failures as they happen and in a summary report

I have a suite of tests that takes a long time to run, so I like to get feedback on failures early. Also it outputs many tests so once CI does fail I want to see the tracebacks at the end of the log

Because installing this in a virtualenv with a version of pytest 2.2.3 meant bad things happened (partial output included below, but safe to assume having a lower version of py.test already installed made things unhappy I think). The install failed, it wasn't able to cleanly back out, then my original py.test was "corrupted", and to fix it I had to manually delete stuff out of the site-packages (hopefully deleting the 2.3 pytest and not my 2.2.3!).

Installing py.test script to (path)/release/bin

error: (path)/release/bin/py.test: Permission denied

----------------------------------------
  Can't roll back pytest; was not uninstalled
Command (path)/release/bin/python -c "import setuptools;__file__='(path)/release/build/pytest/setup.py';exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --single-version-externally-managed --record /tmp/pip-tc50b2-record/install-record.txt --install-headers (path)/release/include/site/python2.7 failed with error code 1 in (path)/release/build/pytest
Storing complete log in (...)/.pip/pip.log

Then:

$py.test tests/unit/formatters/libs/
Exec to gpython at: (path)/release/bin/gpython_opt_off
Traceback (most recent call last):
  File "(path)/release/bin/py.test", line 9, in 
    load_entry_point('pytest==2.2.3', 'console_scripts', 'py.test')()
(...)
  File "(path)/release/lib/python2.7/site-packages/distribute-0.6.24-py2.7.egg/pkg_resources.py", line 588, in resolve
    raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (pytest 2.2.3 (/work/gfe-devel-2.0.0/lib/python2.7/site-packages/pytest-2.2.3-py2.7.egg), Requirement.parse('pytest>=2.3'))