Standard output appended to test results disappears when selecting test run

[timheuer]

Type: Bug

After a test run, the Test Results window shows the standard output. When I select a test/test run, the output disappears and there is no way to make it re-appear.

https://github.com/microsoft/vscode/assets/4821/56292d3b-f603-4e79-b930-d05912802265

This standard output is being appended to the test result model per the C# Dev Kit (@peterwald)

Repo: https://github.com/timheuer/xunitplay (requires C# Dev Kit extension)

VS Code version: Code - Insiders 1.90.0-insider (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T01:34:32.847Z) OS version: Windows_NT x64 10.0.22635 Modes:

System Info

|Item|Value| |---|---| |CPUs|AMD Ryzen 9 3900X 12-Core Processor (24 x 3793)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|127.92GB (95.74GB free)| |Process Argv|--crash-reporter-id 961e68ed-cec6-437f-8e5f-e44a8abbf88f| |Screen Reader|no| |VM|0%|

Extensions (110)

Extension|Author (truncated)|Version ---|---|--- better-comments|aar|3.0.2 tsl-problem-matcher|amo|0.6.2 open-in-github-button|ant|0.1.1 vscode-httpyac|anw|6.14.0 azurite|Azu|3.30.0 npm-intellisense|chr|1.4.5 path-intellisense|chr|2.9.0 esbuild-problem-matchers|con|0.0.3 vscode-markdownlint|Dav|0.55.0 vscode-eslint|dba|2.4.4 npm-browser|den|1.1.4 gitlens|eam|2024.6.417 vsc-material-theme-icons|equ|3.6.0 vscode-open-in-github|fab|2.3.0 azure-storage-explorer|for|0.1.2 visual-nuget|ful|0.2.1 html-preview-vscode|geo|0.2.5 vscode-user-secret-management|gia|1.0.0 codespaces|Git|1.16.22 copilot|Git|1.199.0 copilot-chat|Git|0.16.2024060401 remotehub|Git|0.62.0 vscode-github-actions|git|0.26.3 vscode-pull-request-github|Git|0.88.1 rest-client|hum|0.25.1 svg|joc|1.5.3 vscode-catch2-test-adapter|mat|4.12.0 render-crlf|med|1.8.1 fluent-icons|mig|0.0.18 dotenv|mik|1.0.1 lipsum-generator|MrA|1.2.3 language-gettext|mro|0.5.0 azure-pipelines|ms-|1.228.0 azure-dev|ms-|0.8.3 vscode-apimanagement|ms-|1.0.8 vscode-azure-github-copilot|ms-|0.1.7 vscode-azureappservice|ms-|0.25.2 vscode-azurecontainerapps|ms-|0.7.0 vscode-azurefunctions|ms-|1.15.0 vscode-azureresourcegroups|ms-|0.9.1 vscode-azurestaticwebapps|ms-|0.12.2 vscode-azurestorage|ms-|0.15.3 vscode-azurevirtualmachines|ms-|0.6.5 vscode-bicep|ms-|0.27.1 vscode-cosmosdb|ms-|0.22.0 vscode-docker|ms-|1.29.1 extension-manifest-editor|ms-|0.1.5 csdevkit|ms-|1.7.22 csharp|ms-|2.33.13 dotnet-interactive-vscode|ms-|1.0.5263011 dotnet-maui|ms-|0.12.24 vscode-dotnet-pack|ms-|1.0.13 vscode-dotnet-runtime|ms-|2.0.5 vscode-dotnet-sdk|ms-|0.8.0 vscodeintellicode-csharp|ms-|2.1.11 vscode-aks-tools|ms-|1.4.5 vscode-kubernetes-tools|ms-|1.3.16 playwright|ms-|1.1.6 debugpy|ms-|2024.6.0 python|ms-|2024.6.0 jupyter|ms-|2024.5.0 jupyter-keymap|ms-|1.1.2 remote-containers|ms-|0.368.0 remote-ssh|ms-|0.112.2024053015 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.88.2 vscode-remote-extensionpack|ms-|0.25.0 azure-account|ms-|0.12.0 azure-repos|ms-|0.38.0 azurecli|ms-|0.6.0 cpptools|ms-|1.20.5 live-server|ms-|0.4.13 powershell|ms-|2024.2.2 remote-explorer|ms-|0.5.2024052909 remote-repositories|ms-|0.40.0 remote-server|ms-|1.6.2024053009 windows-ai-studio|ms-|0.3.2 azurerm-vscode-tools|msa|0.15.11 uuid-generator|net|0.0.5 vscode-jest|Ort|6.2.5 vscode-versionlens|pfl|1.13.0 material-icon-theme|PKi|5.3.0 postman-for-vscode|Pos|1.0.3 quicktype|qui|23.0.170 sqlite-viewer|qwt|0.5.6 vscode-thunder-client|ran|2.24.10 java|red|1.31.0 vscode-yaml|red|1.14.0 vscode-marketplace-preview|rob|1.5.1 vscode-coverage-gutters|rya|2.11.1 prompty|Set|0.0.1 svg-preview|Sim|2.8.3 code-spell-checker|str|3.0.1 aspire-gen|Tim|0.3.0 base-ext-sample|Tim|0.0.15 dotnet-containerizer|Tim|0.1.2 mympclient|tim|0.1.6 resx-editor|tim|0.2.21 es6-string-html|Tob|2.15.0 typespec-vscode|typ|0.56.0 vscodeintellicode|Vis|1.3.1 application-insights|Vis|0.4.2 vscode-java-debug|vsc|0.57.0 vscode-java-dependency|vsc|0.23.6 vscode-java-pack|vsc|0.27.0 vscode-java-test|vsc|0.41.1 vscode-maven|vsc|0.44.0 vscode-icons|vsc|12.8.0 volar|Vue|2.0.10 cron-tasks|zok|0.1.2 (1 theme extensions excluded)

A/B Experiments

``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vscod805:30301674 vsaa593cf:30376535 py29gd2263:31024238 c4g48928:30535728 962ge761:30841072 pythongtdpath:30726887 welcomedialog:30812478 pythonidxpt:30768918 pythonnoceb:30776497 asynctok:30898717 dsvsc013:30777762 dsvsc014:30777825 dsvsc015:30821418 pythontestfixt:30866404 pythonregdiag2:30926734 pythonmypyd1:30859725 pythoncet0:30859736 2e7ec940:31000449 pythontbext0:30879054 accentitlementst:30870582 dsvsc016:30879898 dsvsc017:30880771 dsvsc018:30880772 cppperfnew:30980852 pythonait:30973460 jchc7451:31067543 showvideot:31016890 chatpanelt:31014475 bdiig495:31013172 a69g1124:31018687 dvdeprecation:31040973 pythonprt:31036556 dwnewjupyter:31046869 impr_priority:31057980 26j00206:31048877 nativerepl1:31063927 ```

[connor4312]

You can make it reappear by clicking the little "console" icon next to the test run. This isn't shown automatically since the test run is (or should be, fixed in https://github.com/microsoft/vscode/pull/214271) expandable, so it would be confusing when interacting with the twistie.

[timheuer]

Wow, okay, that feels invisible. FWIW in VS these are together.

[connor4312]

Yea, it's the most obvious thing in the world, but is kind of how trees work. Note that you can also click the terminal icon on the test to view output correlated with the test, you highlighted in your screenshot from VS.

At some point we will add stacktrace support in test messages at which point we'll probably have some richer "test detail summary" with information similar to your screenshot in VS.

[timheuer]

I know I'm n=1, but I would have never discovered the 'only visible in hover state' console button. It's weird to me that output associated with the test isn't all in the same place. To me, as a user, I don't know what trees are, I just want to see ALL my output when I select the test. Please consider a change.

[timheuer]

@connor4312 Can you update documentation for Test area? I don't see anything in the TOC for user guide.

It would be good to have a Testing entry in the TOC here, explaining the test explorer, test results output, trees, this console thing, etc. Thank you!

[connor4312]

There is already a WIP on that here :) https://github.com/microsoft/vscode-docs/pull/7310

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[connor4312]

@timheuer fyi the next release of VS Code will ship support for call stacks, by setting the TestMessage.stackTrace property.

UI screenshot in the PR: https://github.com/microsoft/vscode/pull/222126#issue-2417587815