On 2013/04/20 02:46:26, felix8a wrote:
for instance, if I'm working on something involving multiple test
failures, I'd
like to use the test results as a reference for what to do next, and
I'll
iterate over fixing one failure by rerunning just the specific test
failure,
before moving onto the next.
If rerunning one test deletes other test results, then either I have
to rerun
all tests (slow) or save a snapshot of the tests before iterating
(awkward).
I see. I've done that too, now that you mention it. New idea:
Two results directories. One is the current run, and one is the
accumulated runs (the current run is copied into it at the end). The
totals and success/failure output come from the current run, and the
HTML report comes from the accumulated runs.
On a full run (no filter), the accumulated run directory is cleared
before the copy, which gets rid of old bogus data.
Does that sound correct and usable?
https://codereview.appspot.com/8559044/
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
