sound cool. looks like a research topic on it own.
When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding.
So an idea is to diff backtrace before and after the test fails: - revert to last green - replay the test and save the trace - forward to current test and run (test fails) - compare execution paths in order to see the consequence of last change
How would you do this ? Where should I look for materials which can help me coding this ?
I would use MethodWrapper or the like (may be byetsurgeon when available) and you can also have a look at dynamix (a famix extension in the Phd of orla greevy) to model trace. then you keep track of what changed using a changeset and revert. Stef