Repository navigation
Refactor The Rendering of Output In The Test Results Panel #1618
Description
The Problem
Rendering of the text in the Test Results panel is practically unreadable…
Steps to reproduce
- Download and decompress this reproducer
- Open the project in vscode
- Run the sole test in the project
- Observe the Test Results panel
Version Info
Visual Studio Code - Insiders
Version: 1.83.0-insider (user setup)
Commit: 623feb6ddd36…
Date: 2023-09-28T11:51:23.482Z (7 hrs ago)
Electron: 25.8.2
…
OS: Windows_NT x64 10.0.19045
Activity
jdneo commentedon Sep 29, 2023
I can also reproduce it. But when running the second time and so on, it becomes normal.
I guess it's an upstream regression. I need to find a way to reproduce it via the official extension sample, and file an issue at upstream.
lingocoder commentedon Sep 29, 2023
Thanks for looking into this, Sheng Chen (@jdneo)
I haven't been as lucky as you have on retries. In my case, it happens without fail every time I run any test.
Test failures are the worst because the more text output to the view (exception stack traces, for example) , the less readable stuff is.
jdneo commentedon Sep 30, 2023
My feeling is that it's an upstream bug, the VS Code testing API does not expose anything that can control the font/style.
Unfortunately, I tried the extension sample hoping to reproduce it and file an issue to VS Code but failed.
I guess it might be related with the markdown format. This extension uses markdown content to set the test status.
I'm in vacation right now, may not have time to dig deeper into it. If anyone can help investigate the issue, that would be so helpful!
jdneo commentedon Oct 25, 2023
Filed on issue upstream: microsoft/vscode#196521.
WildPenquin commentedon Nov 30, 2023
Hi, any workaround for this problem?
All my tests are useless when run via the plugin. I can not get the output window to normal formatting (sorry for the noise, I know these are not supposed to be support channels).
jdneo commentedon Nov 30, 2023
WildPenguin (@WildPenquin)
I found a workaround for this issue. After running a test, you can click the
deletebuttonThen the output of all the following test execution becomes normal.
WildPenquin commentedon Nov 30, 2023
Sheng Chen (@jdneo),
Thanks, but that workaround does not have any effect here. All test result formats are still wrong / nearly unreadable.
jdneo commentedon Mar 20, 2024
I've tried couple of times and I cannot reproduce this issue with:
Version: 1.88.0-insider
Commit: f7c827a5e0ddbba66425ea54e33430bce8f53c84
Date: 2024-03-20T05:49:22.227Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code-Insiders/1.88.0-insider Chrome/120.0.6099.291 Electron/28.2.6 Safari/537.36
Should be fixed upstream. Please leave comment if it's still observable.