Repository navigation
Test no pass/fail mark whatever the test name (no upper letter) #7859
Description
Environment data
- VS Code version: 1.38.1
- Extension version (available under the Extensions sidebar): 2019.10.41019
- OS and version: Ubuntu 18.04
- Python version (& distribution if applicable, e.g. Anaconda): 3.6.7
Expected behaviour
Using the test tab, after a test is complete (pass of fail) a mark should be displayed.
Actual behaviour
No mark is displayed
Activity
memeplex commentedon Oct 9, 2019
I can confirm this after today's upgrade. It's a regression. There were other problems with unit testing in vscode-python: #7568, #4567. There also is a PR that could fix some of them #7783.
memeplex commentedon Oct 9, 2019
Here is a screencast showing the issue:
Screencast from 09-10-19 19:32:01.zip
astrozot commentedon Oct 10, 2019
Not sure this is related, but after today's update I am having problems running tests. In particular, when I start a test the spinning icon, which normally disappears when the test is completed (to show a green or red icon depending on the result of the test), stays. At the same time, the Log (Window) output shows some errors:
[2019-10-10 14:25:29.550] [renderer1] [error] TreeError [CustomView] Data tree node not found: [object Object]: Error: TreeError [CustomView] Data tree node not found: [object Object]
at Y.getDataNode (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1045:675)
at Y.rerender (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1043:295)
at t.visible.e.map.e (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4974:446)
at Array.map ()
at U.doRefresh (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4974:437)
at process._tickCallback (internal/process/next_tick.js:68:7)
Kindly let me know if I should open a new bug report or if this is related.
memeplex commentedon Oct 10, 2019
Marco Lombardi (@astrozot) it doesn't seem the same bug to me. Could you take a look at my screencast above and check if it looks like your problem? If not, I think you should file a new bug. Several regressions in the already buggy unit test feature popped up during last iteration and it's better to increase visibility. IMO this is not a merely nice-to-have feature and it was somewhat shocking to see that such regressions have slipped through QA.
astrozot commentedon Oct 10, 2019
memeplex I checked already your screencast and indeed it does look quite differently from what I see. I will fill a new bug as you suggests then.
gandroz commentedon Oct 10, 2019
Same for me ! but not sure if it is related
Screencast.zip
astrozot commentedon Oct 10, 2019
Guillaume Androz (@gandroz) I opened a new issue, #7898, you can check if this is also the problem you encounter.
brettcannon commentedon Oct 10, 2019
[ memeplex we edited your ✉️ ⬆️ to come off as more 😃 and less 😠 ]
3 remaining items
karthiknadig commentedon Oct 17, 2019
Guillaume Androz (@gandroz) Can you provide details on particular test framework and if possible a minimal repro? I think it might be related to one of the other issues linked to this, that is the Tree view is failing to update. But just to be sure.
gandroz commentedon Oct 17, 2019
Karthik Nadig (@karthiknadig) please have a look at a dummy repo
It does not have exactly the same behaviour as I describe here, but it has a related bug for sure. Whereas in my current project the icons stay in the
unknownstatus, in this dummy sample repo the status icons eventually loop indefinitely (see the readme)karthiknadig commentedon Nov 6, 2019
Looking at the screencasts and the repo, this issue seems to have the underlying cause as #7898. This has to be addressed in VS Code.
Please up vote the issue here microsoft/vscode#82629 if you have not already done so.