Have you had much of a look at the risk/progress bar? This is quite a useful way to keep tabs on how many tests are failing in the solution. You can dock it to the side of your IDE and make it smaller so it doesn't sit in the way. Admittedly though, this won't show you the details (text) of the failing tests... clicking on the number next to the bar will open up the tests view that can show you this.

I've been thinking about adding some extra hotkeys to allow you to bring up some of the inline information without touching the mouse. Do you think this would solve your problem?

Admittedly, I haven't taken a close look at to see if one of the windows would give me what I need. But it doesn't sound like any of them do, based on your response. Having to keep something docked is much less preferable compared to growl. And if it doesn't give me the failure reason, it's not even as useful as the current story which is mouse hover on red 'X'. When considering growl integration, keep in mind when everything is green. I don't need much info in the growl at all. And I just need the first failure when it goes red. See this screencast to get a feel for what I'm talking about. It's only 5 minutes long. If you want to skip to where the growling begins, start watching at about 2:30. http://www.screencast.com/t/WdP8w7ci9Pm

Yes, more mouseless posibilities.

GoTo + FailingTests
GoTo + ExceptionsFromTests

The Popup-Infos on the red/green points should be accessible by keyboard

+1

I would like to see somewhere WHY a test fails.

Example
--- Output from nUnit runner ---

Test Failure : ChopperTests.EmptyArray_NoneFound
Expected: 1
But was: -1



Great tool BTW!!!