...
| Argument | Mandatory | Description | ||
|---|---|---|---|---|
| Fixtures | ||||
| [fixtures…] | A list of fixture files that should be run. If this is not specified, all the fixtures are tested. The following example runs the test on just two fixture files:
| |||
| General Options | ||||
| --no-compile | Don't compile the lookup database. By default the compile sub-command is automatically executed when running the tests. That can be slow for large databases, in which case you may want to disable the compilation using this flag. | |||
| Snapshots | ||||
| --snapshot | Creates a new snapshot from the current test results. Snapshots are stored on disk (in the snapshots folder by default) and are used to compare the KEE result quality over time. | |||
| --snapshot-message, -m | Add a comment to the snapshot. This implies
| |||
| --diff | Compare the snapshot to the previous snapshot. This outputs how much better or worse the match quality has become. | |||
| Debugging | ||||
| --stats | Outputs a summary for all the missed keywords. This provides a quick overview on what kind of entities are not yet detected as they should. | |||
| --trace STRING | Turns on detailed logging whenever the given candidate is being processed. For example if the lookup database contains an entry called "Acme Inc" then invoking
If this option is present, then the | |||
...