getgauge / gauge-vscode

A Visual Studio Code plug-in for Gauge

Home Page:https://gauge.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Test view container of Gauge is hidden in the Activity Bar in VSCode

zbrea opened this issue · comments

commented

Describe the bug

When creating a new project via the template on a new PC, the ".gauge" folder is never created, while on my old PC everything is fine.
With dotnet it works great too.
I have been with this problem for 2 days, and I can’t find the cause of the problem.

What command(s) did you run when you found the bug?

Create a new Gauge Project ( Template java) 

create  project

Output, stack trace or logs related to the bug

Gauge

Versions

Gauge (Output of gauge -v)

gauge plugins

Operating System information

jdk

IDE information

The .gauge folder is created by gauge during execution, it isn't part of the template. Is there a reason you expect to see this folder?

commented

I know the folder is not part of the model, but the folder is created once the gauge plugin is initialized.
Here it is never created.
You see the PC2 screen:

  • Test view container of Gauge is hidden in the Activity Bar in VSCode,
  • The tests case are not displayed in the test Explorer, because the test explorer is not displayed
  • The "Run Spec | Debug Spec" and "Run Scenario | Debug Scenario " buttons are not displayed, it's as if the gauge-vscode is not recognized.

PC1 : Infos that is in red is not displayed in my new PC (PC2)

PC_OLD

PC2 (New PC)

pc3

commented

I changed the title of the problem to make it clearer.
I can excuse the tests via the command line but I cannot manage the tests with visual studio and especially in debug mode.
In my team we received 2 new pc, and both have the same problem.

Do you have any idea on the cause ?

commented

I was able to solve my problem, I launched my VSCode as administrator, and there the whole problem is solved instantly.
It is possible that my company has restricted the rights on my PC.
Even if I did not find the exact cause but at least the use of VSCode in admin profile it solves the problem.

You can close the bug ! my friend :)

Thanks for sharing your notes @zbrea ! This will help future users.