1 | # Command line overrides
|
2 | Configuration can be bypassed through the CLI (where it makes sense). For example, if you want to enable extensive browser-logging for the next run:
|
3 |
|
4 | ```
|
5 | node ./test/runner.js --browser-verbose
|
6 | ```
|
7 |
|
8 | When you've got your runner-script setup as a npm-script, don't forget to give it an extra `--`. This will pass the arguments to the runner:
|
9 |
|
10 | ```
|
11 | npm test -- --browser-verbose
|
12 | ```
|
13 |
|
14 | ## Commands
|
15 |
|
16 | Command | Description
|
17 | ------- | -------
|
18 | `--api-verbose` | Enables extensive logging
|
19 | `--api-port` | Runs the API on a different port
|
20 | `--api-dir` | Use a different directory
|
21 | `--target-verbose` | Enables extensive logging
|
22 | `--target-command` | The command to run your target
|
23 | `--target-cwd` | The current working directory of the command
|
24 | `--target-checkUrl` | The URL which will be polled to know it's ready
|
25 | `--target-checkInterval` | The speed of polling in `ms`
|
26 | `--target-checkTimeout` | The maximum amount of polling in `ms`
|
27 | `--browser-verbose` | Enables extensive logging
|
28 | `--browser-jQuery` | Injects `jQuery` into the browser
|
29 | `--browser-baseUrl` | The URL to be used as the base for `go()` calls
|
30 | `--browser-readyWhenInterval` | The speed of polling in `ms`
|
31 | `--browser-readyWhenTimeout` | The maximum amount of polling in `ms`
|
32 | `--tests-verbose` | Enables extensive logging
|
33 | `--tests-glob` | Pattern to find your tests
|
34 | `--tests-mocha-grep` | The `grep` option for Mocha
|
35 | `--tests-mocha-ui` | The `ui` option for Mocha
|
36 | `--tests-mocha-reporter` | The `reporter` option for Mocha
|
37 | `--tests-mocha-timeout` | The `timeout` option for Mocha
|