Open stevejalim opened 10 years ago
How about we archive all previous failures on the next run - so test_rerun.txt
gets re-written as test_rerun-{{timestamp}}.txt
each time it's run.
I hear you. That might leave behind a lot of files, tho.
How about a syslog-style pattern where we generate test_rerun.txt
as latest, after suffixing the previous one as test_rerun.txt .0
....1
....2
etc
And then allow a max num of those to exist...?
Ugh. Complex tho
@stevejalim it may not be that hard if you use logger
and its RotatingFileHandler
. The rewrite of this module will become less tedious, it may also partially solve #6. Reusing the rerun logs would become a burden, though, but if it would really be optional, masochist developers may want to turn it on :)
This would cater for the scenario when there is more than one failing test, but one is fixing up just one test at a time. Currently, running a single test will zap the existing test failure list.