Open correct position in Pytest Test Log with a single click on any test

[andrmueller]

Hey there!

I really like how you move on with this extension. Especially testing got way better!

The Problem

There is one single thing that slows my developer process down quite a bit:
When clicking on a test that is currently executed or has been executed sometime before in the current VS code window the output of this specific test does not open up automatically. The output to show would be the Python Test Log.
i.e. with pytest:

=================================== FAILURES ===================================
___________________ test_z ____________________

line 1
line 2

line3
...

What I tried

Using the shortcut: "testing.showMostRecentOutput" -> "when": "testing.hasAnyResults".
Sadly this does not open up the Python Test Log output, but a terminal with the test run output which IMHO is not readable enough regarding formatting to be used to debug errors in tests.

The most recent output looks something like this when using pytest:

Current working directory: /...
Workspace directory: /...
Run completed, parsing output
./tests/.../test_xy.py::test_z Failed: <error>
line 1
                                                                line 2

                                                                                               line 3

The Python Test Log output looks way cleaner and it's the actual pytest/unittest output which people are used to.

Current circumvention

• Execute 1 or multiple tests by using the Testing panel
• Open up the output with a shortcut ("python.viewOutput")
• Use the mouse to open Python Test Log channel

• Scroll to the test I'm interested in logs or errors manually or by using the search in the output window using the test name

Feature Request

• Execute 1 or multiple tests by using the Testing panel
• Click on any of the tests with a single click
• Pytest Test Log output is opened
• The window scrolls to the start or end of the test output for the clicked test

[brettcannon]

Converted to an issue to make this a feature request.

#17371