Fix test script quoting to run properly on Windows

[aarongoldenthal]

The current test scripts single quote the test pattern glob, which runs properly in Linux and macOS, but on Windows it results in no tests found. This then passes since no tests failed, as seen in the following log from here.

Actions Log

Run npm test

> [email protected] test
> npm run test-coverage && npm run verify-coverage && npm run test-integration

> [email protected] test-coverage
> nyc --reporter=text --reporter=html mocha --file test/unit/setup.test.js 'test/unit/**/*.test.js' --recursive

Warning: Cannot find any files matching pattern "'test/unit/**/*.test.js'"

  0 passing (1ms)

----------|---------|----------|---------|---------|-------------------
File      | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s 
----------|---------|----------|---------|---------|-------------------
All files |       0 |        0 |       0 |       0 |                   
----------|---------|----------|---------|---------|-------------------

> [email protected] verify-coverage
> nyc check-coverage --lines 90 --functions 90 --branches 90

Warning: Cannot find any files matching pattern "'test/integration/**/*.test.js'"
> [email protected] test-integration
> mocha --file test/integration/setup.test.js 'test/integration/**/*.test.js' test/integration/teardown.test.js --recursive --timeout 20000 --slow 5000

  0 passing (0ms)

This traces back to the original conversion from make to npm scripts in 40ba01a, with the note "quote globs in scripts to avoid missingsubdirectories". On Linux/macOS without the quotes, or with double quotes, the tests/unit/lib/reporters/* tests are not run, although on Windows the tests all run in those cases. Mocha was updated in #256 (from 10.3.0 to 11.1.0), and this appears to have been missed (tests run as expected in the previous commit).

Keeping the globs, double quoted, but without the --recursive flag seems to work on all platforms. I also added the --fail-zero flag, which will fail if no tests are found.

This appears to be an instance of mochajs/mocha#4186.

[jpw]

Nice spot and fix, thanks @aarongoldenthal :)