Provide history of failed tests
When working on a project where NCrunch is running (all) the tests automatically in the background, some tests occassionally fail and then suddenly pass.
I would like to have some kind of history for failed tests so that I can even later on delve further into the failed tests to figure out what's going wrong.
In addition it would be nice to be able to configure the time span (or number of tests runs) for that historical data to limit the memory consumed (I could imagine that using that feature on large projects will have a significant memory impact).
Richard Lawley commented
This would also make things useful to make it obvious which test you just broke or fixed when there are many broken (or not yet implemented!) tests.
@Darius: I think it is even more common when having grid nodes so tests might fail on some nodes but not others, e.g. node isn't performant enough for specific tests, have incorrect test filters, can't reuse cached data etc. I would find it valuable be able to "post review" the reasons for failure. (Also NCrunch seems to sometime re-run a test yet again when pinning it, let it be bug or not, causing my red test I want to investigate to suddenly become green with the reason of previous failure is nowhere to be found).
Darius Damalakas commented
Seems like an edge case scenario to me. I do get run into situations when sometimes a test passes, and when run in conjunction with the others it passes, but then it's about test isolation. Don't think you need this feature in order to resolve this. (If i've understood your intention right)