Workaround: "open" is not crossplatform; and yet is not required by this continuous integration system. Adding the alternative test-ci-cover option

D:\githubforks\frame----i18n-dev-fork>npm run test-cover

> frame@1.1.0 test-cover D:\githubforks\frame----i18n-dev-fork
> node ./node_modules/lab/bin/lab -c -r html -o ./test/artifacts/coverage.html && open ./test/artifacts/coverage.html

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

npm ERR! frame@1.1.0 test-cover: `node ./node_modules/lab/bin/lab -c -r html -o ./test/artifacts/coverage.html && open ./test/artifacts/coverage.html`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the frame@1.1.0 test-cover script.
npm ERR! This is most likely a problem with the frame package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./node_modules/lab/bin/lab -c -r html -o ./test/artifacts/coverage.html && open ./test/artifacts/coverage.html
npm ERR! You can get their info via:
npm ERR!     npm owner ls frame
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "T:\\node\\node-v0.10.33\\\\node.exe" "T:\\node\\node-v0.10.33\\node_modules\\npm\\bin\\npm-cli.js" "run" "test-cover"
npm ERR! cwd D:\githubforks\frame----i18n-dev-fork
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     D:\githubforks\frame----i18n-dev-fork\npm-debug.log
npm ERR! not ok code 0