Tired of searching for those few red and yellow rows in a sea of green...

Not sure if this is better than a "v" character, but have you considered ↓(↓) instead?

Overall .. this is a nice improvement for simpletest

Hmm... what about this: ▼(▼) I suppose I'm just looking for something more semantically correct

I think this needs at one other look before it can be marked RTBC ... Everything looks good to me but I'm not familiar enough with the ins and outs of the simpletest module to know if there are any weird ramifications of this. I doubt it, but...

What about a title attribute or something like that explaining where the link goes to?

+++ modules/simpletest/simpletest.pages.inc	17 Oct 2010 16:44:05 -0000
@@ -225,6 +225,7 @@
+    '#title_tag' => simpletest_tag(),

@@ -252,8 +254,9 @@
     foreach ($assertions as $assertion) {
...
+      $row[] = ($ok ? '' : simpletest_tag(TRUE)) . $assertion->message;

It would be much more cleaner if the jump ID incrementing logic would be part of the theme function, instead of the helper function.

Furthermore, I don't think we want jump IDs and links for every single failing assertion in a row that merely point to the next line. That's too much clutter. Instead, we need some more intelligent logic that jumps to the next block of failed assertions. Possibly output that link for the last failed assertion of the last block of failed assertions.

+++ modules/simpletest/simpletest.pages.inc	17 Oct 2010 16:44:05 -0000
@@ -245,6 +246,7 @@
+      '#collapsed' => TRUE,

The change to reverse the #collapsed logic is not required for this patch.

+++ modules/simpletest/simpletest.pages.inc	17 Oct 2010 16:44:05 -0000
@@ -335,6 +344,19 @@
+  return '<a id="jump-' . $id . '" href="#jump-' . (++$id) . '" style="position: relative; left: ' . ($adjust ? '-1.8em' : '-1em') . '; top: ' . ($adjust ? '-4em' : '0') . ';">&#9660;</a>';

Obviously, inline styles are discouraged. That's what CSS classes are for.

13 days to next Drupal core point release.

I like this patch too but I have my doubts over inline styles and even the inline HTML. Can you or someone else reroll using l() and a CSS file please? I do not think we need to move the counter -- having the counter in simpletest_tag() is better in the rare case you have several simpletest results on one screen. And, I do not think it's such a clutter either.

So I think this classifies as novice material now -- just convert the link to a proper Drupal link + CSS please. Thanks!

I like this. I will let the maintainers decide whether they like it too.

Hrm. The first attached screenshot shows what I see with this patch applied.

The resulting UI of this is not really great. The arrows/jump-links appear in very unusual positions - partially clashing with the UI patterns of existing page elements.

I spent quite some time thinking about this, since I investigated similar ideas for potential inclusion in http://drupal.org/project/admin_ux

Meanwhile, I think an actual improvement would be to have a "sticky test results navigator."

We not only want to navigate in test results. The next best most cumbersome UI operation is to run the failing tests again, or alternatively, get back to the test overview/list page. In both cases, that usually involves quite some page scrolling, too - which is the reason for why I see these issues to be closely related, or actually, to be the same UI/UX problem space.

Thus, I strongly believe we should implement this navigator instead. It behaves pretty much like the sticky table headers, but appears above them. The previous/next links are purely JS-driven and do not require any server-side changes at all.

Here is a quickly mocked screenshot for that:

Let's try to fix the issue with js scrolling navigation.

I don't get why there insn't also just a toggle, to only see the fails.

I don't get why there insn't also just a toggle, to only see the fails.

It isn't convenient for me. When error occurred I would like to know what happened before the fail. So I need to see green messages as well as verbose messages in close vicinity to the fail message.

This is really really nice! Posting a screenshot to show.

This is just a cleanup of some pieces, though it feels that sun's idea seems to be the best in terms of experience and simplicity.

Triaging issues in simpletest.module to determine if they should be in the Simpletest Project or core.

This looks like it a simpletest module issue, changing the project.