'npm test' syntax not working on windows

[Guuz]

Using Windows 8 and Git Bash the following is not working:

In package.json the npm test script is declared as following:

"scripts": {
  "test": "node lib/cli.js spec/basicConf.js; node lib/cli.js spec/altRootConf.js; node_modules/.bin/minijasminenode jasminewd/spec/adapterSpec.js"
},

Running this I get the following error:

module.js:340
    throw err;
          ^
Error: Cannot find module 'C:\Projects\protractor\spec\basicConf.js;'

I believe the semi-colon is to blame. When I replace those by 1 or 2 ampersands it works.

node lib/cli.js spec/basicConf.js & node lib/cli.js spec/altRootConf.js

The problem then is that the third (last) command starting minijasminenode gives this error:

'node_modules' is not recognized as an internal or external command,
operable program or batch file.

I don't know how to fix this... But at least the first two statements/test scripts work. Maybe someone knows how this "npm test" can be declared so it works cross platform?

[Guuz]

Could anyone confirm if this is the same on their machine and perhaps how to fix it?

[juliemr]

Fixed w/ manage-webdriver start

[juliemr]

Sorry nevermind, this is a different issue. Do you mean npm test?

[Guuz]

@juliemr: yes, this is about the npm test command.

[axemclion]

I am able to run npm test by renaming the test.sh to test.bat. However, the unit tests are still not running and I need to manually run them for each file using

node_modules\.bin\minijasminenode jasminewd\spec\adapterSpec.js spec\unit\config_test.js

Note that the unit tests are failing because of the paths like this. In case of Windows, path.resolve will be of the format c:\.... When doing a toMatch in minijasmineNode, the regexes are tested on paths that are not normalized.

[axemclion]

Also trying to fix this by converting test.sh to test.js so that windows can also run it - #635

[juliemr]

Done with #635 Thanks @axemclion