In the NCrunch Tests window there is a Processing Time column. It is my understanding that the column shows the time it took to execute the thing on that line. However, the view is a tree view, meaning tests are nested inside of their classes. In order to find the tests that took the longest, I have to expand every class (which takes a very long time when you have 100s of test classes) and scroll through the list to find the long-running tests.

If the "Processing Time" column for a class displayed the total time it took to process the entire class (meaning the overhead of the class plus the time taken for every nested class and test method inside of it then when I sorted by Processing time slow tests would cause their class to bubble up to the top when sorted and the method would then bubble up to the top of that class, making it easy to find my slow tests.

As an example, imagine you have two classes, each with one test method inside of it. Class A has a long overhead and takes 1 second to startup. Class B has very little overhead and starts up in 1 millisecond. Inside of class A you have method Foo (A.Foo) which is really fast. Inside of class B you have method Bar (B.Bar) which takes 10 seconds to execute. In this scenario, if you run both tests (A.Foo and B.Bar) and tell NCrunch to sort by Processing Time A will show up above B and both will have their methods collapsed (hidden). In order to find my slow (10 second) test I have to expand every class and manually look through all of the processing times to find the slow one.

The above example is simplified, but you can imagine how difficult this can become when you have 100s of test classes (some nested) and 1000s of tests.