Override pytest's exit code 5 for "no tests were run" about pytest-testmon HOT 10 CLOSED

Why is this ticket closed? I just now was hit by this and had to make a workaround... Have I done something wrong or do I need to do something different?

from pytest-testmon.

My workaround was to make my program explicitly know about this exit code and treat it as zero if testmon is in use.

from pytest-testmon.

Yeah, I understand the use case. This would idally by done by storing the
results from previous run and returning a union of stored and new test
results (the proper exit code would be produced automatically)

On Wed, Dec 16, 2015 at 9:15 PM, Daniel Hahler [email protected]
wrote:

py.test will exit with code 5 in case no tests were ran (
pytest-dev/pytest#812 pytest-dev/pytest#812, pytest-dev/pytest#500
(comment)
pytest-dev/pytest#500 (comment)).

I can see that this is useful in general, but with pytest-testmon this
should not be an error.

Would it be possible and is it sensible to override pytest's exit code to
be 0 in that case then?

My use case it using pytest-watch and its --onfail feature, which should
not be triggered because testmon made py.test skip all tests.

—
Reply to this email directly or view it on GitHub
#31.

from pytest-testmon.

@tarpas
Any update on this?
Can you provide more hints to fix this?

While pytest-watch has a patch by now that handles it, it's still an issue when running py.test --testmon with other tools.

from pytest-testmon.

This is going to be implemented via #13

from pytest-testmon.

@blueyed Do you want to take a stab on it?

from pytest-testmon.

@tarpas
Thanks for the offer and notification, but that's too much for me currently.
Maybe that would be a good topic for the pytest sprint!?
Also the whole topic of making this a first-class pytest plugin.
Are you coming?

from pytest-testmon.

what was your workaround @boxed ?

from pytest-testmon.

This was closed because I thought #13 fixes it, sorry.

from pytest-testmon.

Fixed in v 1.3.0.

from pytest-testmon.