`tns test init --framework qunit` fails on windows

[dtopuzov]

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

• CLI: latest
• Cross-platform modules: latest
• Android Runtime: latest
• iOS Runtime: latest
• Plugin(s): No

Describe the bug
tns test init --framework qunit fails on windows

To Reproduce

tns create TestApp
cd TestApp
tns test init --framework qunit

=> Fails with non zero exit code.

Expected behavior
tns test init to work properly.

Additional context
Looks to be caused by the fact that there is no qunit@2.0.0 version on npm and in karma-qunit package.json we have:

"peerDependencies": {
    "qunit": "^2.0.0"
  },

Workaround
Execute npm i qunit@2 --save-dev before tns test init.
Note that tns test init will still fail, but after that tns test will be fine.

[Fatme]

The issue is windows specific and can be reproduced on cmd console with the following nodejs script:

const childProcess = require('child_proccess')
childProcess.spawnSync('npm.cmd', ["install", "qunit@^2.0.0"])

The problem is the ^ symbol is not provided to npm and it tries to execute npm i qunit@2.0.0. As such version doesn't exist, it fails with an error.
The workaround here is to replace ^ with ^^^^.

const childProcess = require('child_proccess')
childProcess.spawnSync('npm.cmd', ["install", "qunit@^^^^2.0.0"])