When I'm running my unit tests, and I get failures, all I see is the red "Failed" message. I don't know why it failed.
To find out, I have to use my mouse to click on each failure to "open" its details area, where the message is included.

However, I noticed that we're also displaying the running time for the tests. Personally, I don't care how many seconds
a test took to run - but I -do- want to see the message that the test failed with! Sometimes I can immediately tell what
the issue is so I can continue fixing my test or the associated behavior. Other times I can tell it's a failure I can
ignore (for example that a performance test failed because it took too long, which is expected if I had the test
suspended while debugging part of it).

So here's an idea -- why don't we display the status messages from each test right in the test summary?

I liked that idea so much that I went ahead and patched my own clone to do that - and I've been using it that way for a
couple of days now. And I'm convinced it's a big improvement - at least for my workflow. And I don't see how this
wouldn't be an improvement for anyone.

I'll attach a couple of screenshots: first a screenshot which shows what the junit window looks like today - you get
some failures, with no clue as to why. You do however know how many milliseconds each test took ;-)

In the second screenshot, junit-proposed.png, you can see what happens if we include the status message right in the
display name for each node. In many cases, this is enough for me to decide what the problem is and decide which test to
focus in on. (And for example after making a change to the code, running the test again and seeing the same message
tells me more than having to click my way down to find out if this is the same or a new failure.)

Finally, the third attachment is my patch to do this to the Junit module. I suspect the patch for the Ruby test runner
is very similar.