search

hbenl / vscode-test-explorer

The VS Code Test Explorer extension
MIT License
215 stars 55 forks source link

Test UI does not appear in activity bar #152

Closed dschuessler closed 4 years ago

dschuessler commented 4 years ago

I installed the Mocha Test Explorer, the Angular/Karma Test Explorer and with them the Test Explorer UI. You can see them installed in the screenshot. Yet the lab flask icon does not appear in the activity bar and the UI does not seem to be present or accessible.

Bildschirmfoto 2020-07-17 um 22 21 17

VSCode 1.47 macOS 10.14.6

hbenl commented 4 years ago

Did you set testExplorer.hideWhen in your VSCode settings? Otherwise I don't know how this could happen.

dschuessler commented 4 years ago

Thanks for responding. I have this setting set to "never".

hbenl commented 4 years ago

Thanks for responding. I have this setting set to "never".

Hmm, interesting. In this case it should always appear in the activity bar. I still can't figure out how it is possible that it doesn't.

dschuessler commented 4 years ago

If there is any more information I can provide from my end, let me know.

jounathaen commented 4 years ago

Hi, I have the same problem with

jounathaen commented 4 years ago

I found out that in my case the problem seems to be the VSCodium package repository. It seems to be different than the MS repository and for whatever reason the version from that repository does not work. Using the Microsoft Repository, the extension works again.

hbenl commented 4 years ago

I found out that in my case the problem seems to be the VSCodium package repository

It turns out that the version of the extension published on open-vsx.org was broken. I republished it and now it should work.

hbenl commented 4 years ago

@dschuessler I just tried installing the Mocha and Karma Test Explorers in a fresh install of VSCode in MacOS 10.15 and it did work as expected (i.e. the Test Explorer UI appears and I could interact with Mocha tests). You could try the same (e.g. in the Guest user account of MacOS or by renaming ~/.vscode and ~/Library/Application Support/Code) to see if this issue is triggered by some other extension or some VSCode setting.

dschuessler commented 4 years ago

@hbenl This is not necessary. I had installed the extension via VSCodium as well and just checked that it is not a VSCodium related error by starting up VSCode using the same extension directory. So VSCode was using the version from Open VSX as well. It did not occur to me that the installation source could be important for the reproduction of the error.

I updated the extension and the icon is appearing now. Thank you for investigating this!

hbenl commented 4 years ago

It did not occur to me that the installation source could be important for the reproduction of the error.

It didn't occur to me either. Thanks to @jounathaen for pointing this out!