Gauge Initialisation not showing Folder in VS

51 views
Skip to first unread message

Pete Morrell

unread,
May 31, 2020, 10:37:45 AM5/31/20
to getgauge
Hi
Sorry I'm new to this game - and sorry for such a basic question...
I've followed the installation instructions on Windows 10, and installed Gauge 1.0.6 and the VS extension 1.45.1 i.e. all the latest!
I've followed the setup Test Project instructions (https://docs.gauge.org/getting_started/create-test-project.html?os=windows&language=javascript&ide=vscode) and created a JS Test Project, but there are no folders created under the Test Project either in VS or on the Windows filestore.  The instructions suggest I should get a set of folders, so I could for example run an example test spec as provided by the installation.
I've attached a VS screenshot.

I must be failing somewhere very basic.

Can anyone suggest what I've missed?

Pete

Gauge Initialisation.JPG

Srikanth V

unread,
May 31, 2020, 10:53:23 PM5/31/20
to getgauge
Hi,

Welcome to Gauge!

Gauge 1.0.8 is out for some time, please try to upgrade.

Have you tried creating a project from command line? In windows, please open `cmd.exe` (hint: in your windows application menu, type `cmd` to see suggestion, it may say "Windows Command Prompt").

You should see a terminal. You can run the below commands (in the same order):

- gauge -v
- cd %TEMP%
- mkdir gauge-testing
- cd gauge-testing
- gauge init js

This should create the project.

Please post back with the results (if possible, please share the output of the above commands), we'll then know if the issue is with gauge core, or with the gauge-vscode extension.

best
Srikanth

Pete Morrell

unread,
Jun 1, 2020, 10:17:27 AM6/1/20
to getgauge
Thanks Srikanth
I followed your instructions below, and got an error saying the js plugin hadn't been installed at the 'gauge init js' command.
I don't remember receiving an error when I'd completed the Gauge installation with Javascript plugin (although I might have done!).
I did a bit more investigation, and tried to reinstall the js plugin from the command line, and it told me 'npm' wasn't valid.  This should have rung a bell!

At this point, I thought I'd just reinstall from scratch and follow the default settings.  I uninstalled Gauge and Visual Studio, then went back to the Gauge documentation.
Gauge 1.0.6 was where I was pointed to from the Gauge documentation (Installing Gauge> Install using Windows Installer> Windows Installer (Attachment 1 Windows Install).  I note you suggested using 1.0.8 - maybe this link should point to wherever the latest stable version is?  I selected the Javascript Plugin to install, and the installation completed without any errors.
I then selected the 'Latest VS code' in Step 2 and VS was installed successfully.
I then selected the 'Gauge Extension' in Step 2, and completed the installation successfully.
I then went into 'Create a Testing Project'.  This specifies the System Requirements for node js.  At this point I hadn't done anything about node js, and didn't realise I should have this installed.  Maybe there should be a 'heavier' warning at this point?
When I tried to create the project in VS, I got an error saying a folder wasn't available.  I recognised this as the Folder I had setup the first time round (any idea why this isn't updated on the reinstall - where is this location stored?).  I recreated the Folder manually and continued.  VS showed 'Initializing Project' in the bottom bar, and completed.  The same screen was shown i.e. the Folder was there but no contents.

I then went through your instructions again
I got the failure at 'gauge init js', which gave...
C:\Users\pedzh\AppData\Local\Temp\gauge-testing>gauge init js
Downloading js.zip
Copying Gauge template js to current directory ...
Compatible language plugin js is not installed. Installing plugin...
......................
Failed to install plugin 'js' version 2.3.11.
Reason: exec: "npm": executable file not found in %PATH%

C:\Users\pedzh\AppData\Local\Temp\gauge-testing>

So it looks like it can't find npm - I realise this was actually mentioned in your documentation when I went to Create a Project! - so my bad there!

My PATH is
C:\Users\pedzh\AppData\Local\Temp\gauge-testing>PATH
PATH=C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Gauge\bin;C:\Users\pedzh\AppData\Local\Microsoft\WindowsApps;C:\Users\pedzh\AppData\Local\Programs\Microsoft VS Code\bin

C:\Users\pedzh\AppData\Local\Temp\gauge-testing>

I looked for npm on my PC, but couldn't find it.  So googled it and realised I needed node js installed.
I went through this, which completed successfully.

Create Testing Project then worked!  So I think this is more down to user error than anything else!  The possible improvements in bold above are probably 'nice-to-have'.

Thanks
Pete
Reply all
Reply to author
Forward
0 new messages