[pytest-dev] re-running pytest on file changes

[Tibor Arpas]

Hi,

I'm trying to wrap my head around this subject.

Is there a strong reason why the -f looponfail option is inside a plug-in?
My hunch would be to do it as a separate, flexible, command, but that's
just feelings without any experience.

Poll: Do you guys use looponfail? Has it been working good? Does it play
nice with other tasks you might want to do on file changes? What other
tools do you use for repeated tasks on source code changes?

What's the situation at the moment with --looponfail and --looponchange? Is
it going to be inside pytest_cache which will go into core? Or it will be a
different plug-in?

I've seen
https://bitbucket.org/pytest-dev/pytest/commits/b5727cc6632c/

and the "take in cache" PR.


Tibor
P.S. some more thoughts about the same functionality are here:
https://github.com/tarpas/testmon/issues/4
and a script whith callbacks for every success and failure:
https://github.com/blueyed/testmon/blob/tmon-improvements/testmon/tmon.py
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150327/a09d699c/attachment.html>