This project is read-only.

Request - Monitor nUnit timings for interesting changes

Oct 2, 2009 at 12:47 PM

We have a rather large test-collection, and it is not enough to monitor the entire build-time to see if performance issues have been introduced.

It could be nice if it could compare the timings of the different tests, and see if there are interesting changes:

1) If the moving average time for a test is 1 sec and it suddenly takes 10 secs then trigger.

2) If the moving average time for a test is 10 sec, and it suddenly takes 1 secs then trigger.

The main problem here is to configure a way to ignore normal flux in timings. Since a test that takes 1 sec. can go from 0.5 sec. to 1.5 sec. without actually being an issue.

Would it make sense to include this in CCStatistics ?