29 Oct
2012
29 Oct
'12
6 p.m.
Dave Abrahams <dave <at> boostpro.com> writes:
What I always wanted was something that would automatically run all the tests that failed first and schedule all the tests that succeeded last, after any that didn't run at all. Obviously that requires keeping some state around between runs.
With a little effort of maintaining the state somewhere we can add 2 command line arguments: test.exe --save_state=<location> test.exe --run=@failing test.exe --run=!@failing Second is an existing command line argument, but we'll need to add handling to "special" label. Gennadiy