Allow expanding test output in results view

[Gert-dev]

Hello

The results view currently already shows the error message of the test when it failed. Would it be possible to allow expanding this column to show the remainder of the output? If the output spans several lines, the remainder of the output is currently cut off.

I understand that you can use the raw output view for this, but it seems the raw output view should be necessary only in the rarest of cases where the specific test runner is doing something unsupported or outputting something that can't properly be processed by the provider.

I believe PhpStorm even shows some kind of tooltip with the output when you hover over the gutter mark in the editor itself, but I believe that even simply putting it in the results view will go a long way.

Finally, I see that clicking currently navigates to the test itself. Perhaps single-clicking can be used to expand the test output and double-clicking (or clicking the location) to actually navigate to the test?

Thanks in advance

[yacut]

Hello. Thanks for the issue. The "re-sizable columns" feature is already in roadmap. And I should think about single-/double- click behavior.

[Gert-dev]

I see you added the Need a concept flag and I wanted to try and provide you with some more idea's regarding this (even though I'm not a designer):

• As mentioned before, you could use a click to "expand" the row, which would show another row below it with the raw output of the error. I realize now that this can be problematic if the error message output is large, which can happen if you're comparing subsets of arrays in e.g. PHPUnit.
• I believe JetBrains IDE's show a short summary of the error (pretty much what we already have in tester) and present you with a dialog containing a scrollable view with the raw error output. This could work, but I believe having windows open is cumbersome for the user, especially since in JetBrains IDE's the window can be left open whilst in Atom windows tend to disappear after they lose focus.
• We could also open an actual editor with the test output, but I think this suffers from the same problem as using a window does: it takes away focus and needs to be closed again constantly.
• Perhaps what you're already doing with the Tester Console is a good idea: use a separate dock/tab for output that is updated and activated as soon as you click an issue in the tester results.

The last option currently feels like a good compromise, especially since it allows you to quickly switch between single tests results and you can just leave the tab open and hide it when you don't want to see it, much like the rest of the tester's docks. Additionally, the tester console sometimes shows an aggregation of all errors from all tests that failed, whilst having such a separate dock would allow you to quickly filter by the error message for that test.

Hope this helps!