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

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.

Start by running the reported Windows reproduction with tns create TestApp, then tns test init --framework qunit; inspect how the CLI resolves and installs the QUnit and karma-qunit dependencies. The workaround and peer dependency details identify the dependency setup as the focus. Done means initialization exits successfully without the manual qunit@2 installation and the subsequent test command works.