On 2013-10-10 19:00, Martin Owens wrote:
On Thu, 2013-10-10 at 16:14 +0100, Alex Valavanis wrote:
two separate executable scripts
Not yet. And while the python is pretty hairy (needs some code review) it should be possible to make it do what you want without too many issues.
Guiu, Tav; what do you think? Would it be easy enough to modify and would you like to patch it or should I?
It's not completely clear to me what you need exactly (just a change/no change answer, a number of failed/succeeded tests, ...?), but there is currently no separation between good and bad tests. In particular, a test could have (and some do have) both known good and bad references related to it.
However, you can simply pass a list of tests to perform on the commandline if you want (or use a directory, as suggested by Alex). Any results are kept track of in teststatus.json. This file gets read and updated each run (rather than replaced with new results), so it would be possible to just run tests that failed/succeeded the last time (based on a commandline option), if that's what you need. If I can be of any help (since I actually wrote that dense bit of Python code), just ask.