[TIP] "midget" pony continuous integration tool

Laura Creighton lac at openend.se
Wed May 6 20:26:07 PDT 2009


In a message of Thu, 07 May 2009 10:45:24 +1000, Ben Finney writes:
>holger krekel <holger at merlinux.eu> writes:
>
>> FYI, with py.test you can do: 
>> 
>>     py.test --looponfailing 
>> 
>> which will run all your tests, then wait for changes,
>> re-run only your failures, wait for changes, ..., 
>
>So, if I make a change to fix one of the failures and inadvertantly
>break a test that previously succeeded, I can go an indeterminate number
>of code-test cycles before I find out about it?
>
>That seems like the canonical reason why “run the entire unit test
>suite every time” is good practice, and I can't see why the above
>behaviour would be desirable.
>
>Ben Finney

Because running all the tests takes 2.5 hours.

Laura




More information about the testing-in-python mailing list