Why Slow Report

It would be great if I could bring up a report that contained a list of the slowest things in the solution from NCrunch's perspective so that I've always got a hit list to make things faster.

Things that come to mind:
- Project that are slow to build
- Slowest tests
- Slowest test fixtures

I also find myself sorting stuff by time spent, looking for what tests took longer than I care for... I don't quite follow what some of the durations represent though, especially if there are tests that timed out for example.

Some sort of metrics on the time spent on given lines would be nice too - seeing hotspots inline is great, but if it already collects that information, it'd be nice to also have a general overview of the slow points in the code.

Hi,

Thanks for the suggestions! A 'hot spot' view is definitely a nice to have. I've been thinking about ways this could perhaps be included in the metrics view.

Something that I think will help with finding slow tests and projects would be to introduce different grouping options in the Tests Window. Although the Tests Window already lets you sort by execution time, the sorting gets disrupted by the groups, making it hard to actually find the slowest tests. If it's possible to flatten the try entirely, the sorting would be much more effective. Let me know what you think.


Cheers,

Remco

A flat view with test execution times would be great.

I use TeamCity for our build server and it offers a flat view of test execution times which I find handy, when I take the time to open it up and look. It would be great to have such information close at hand.