iancmyers / whiteglove Goto Github PK

View Code? Open in Web Editor NEW

10.0 10.0 2.0 75 KB

Find the dirty tests making a mess of your test suite!

License: MIT License

JavaScript 100.00%

whiteglove's People

Contributors

Stargazers

Watchers

Forkers

strugee

whiteglove's Issues

Output language should specify when spec the leaky tests affect

Add verbose flag for logging and debugging

Feature request: seek out masked failures

I'd like to pass an entire test suite to whiteglove, and have it figure out which of the tests fail when run in isolation - ie, which tests are relying on a different test's global changes or stubs/spies.

Warn when test runner does not run correctly

Refactor and consolidate output generation

The output generated for whiteglove bisect and whiteglove iso is essentially the same, but is produce by two different functions.

Support multiple paths representing "the suite"

Just like mocha accepts N paths, it would be ideal if whiteglove accepted them too.

Add tests for error cases

`--help` errors out

$ whiteglove --help
whiteglove spec.js dir [options]

  -r, --runner String      Command used to run the test suite - default: node
  -p, --patterns [String]  Filename patterns matching your spec files - default: ['.js']
  --verbose                Output a ridiculous amount of information
  -h, --help               Display this helpful help menu
$(npm root -g)/whiteglove/bin/whiteglove.js:5
  if (!run || run.reportedTests().length) {
                  ^

TypeError: run.reportedTests is not a function
    at $(npm root -g)/whiteglove/bin/whiteglove.js:5:19
    at Object.execute ($(npm root -g)/whiteglove/lib/cli.js:188:12)
    at Object.<anonymous> ($(npm root -g)/whiteglove/bin/whiteglove.js:4:5)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3

Create a CHANGELOG.md and keep it up to date with releases

Add timing to output

We should output how long it took to complete the task.

Concurrency of 0 with only one CPU

I'm working on a virtualized server which only has one CPU allocated to it. When I run Whiteglove like so:

$ ./node_modules/.bin/whiteglove --verbose -p '[-test.js]' -r ./node_modules/.bin/vows bisect test/event-test.js test

I get:

runner: ./node_modules/.bin/vows, patterns: [-test.js]
verbose: Finding all test paths in test
verbose: Found 190 test files
verbose: Starting search with concurrency of 0

and then the command exits.