cucumber.api.cli.USAGE.txt Maven / Gradle / Ivy
Usage: java cucumber.api.cli.Main [options] [[[FILE|DIR][:LINE[:LINE]*] ]+ | @FILE ]
Options:
--threads COUNT Number of threads to run tests under.
Defaults to 1.
-g, --glue PATH Where glue code (step definitions, hooks
and plugins) are loaded from.
-p, --[add-]plugin PLUGIN[:PATH_OR_URL]
Register a plugin.
Built-in formatter PLUGIN types: junit,
html, pretty, progress, json, usage, rerun,
testng. Built-in summary PLUGIN types:
default_summary, null_summary. PLUGIN can
also be a fully qualified class name, allowing
registration of 3rd party plugins.
--add-plugin does not clobber plugins of that
type defined from a different source.
-t, --tags TAG_EXPRESSION Only run scenarios tagged with tags matching
TAG_EXPRESSION.
-n, --name REGEXP Only run scenarios whose names match REGEXP.
-d, --[no-]dry-run Skip execution of glue code.
-m, --[no-]monochrome Don't colour terminal output.
-s, --[no-]strict Treat undefined and pending steps as errors.
--snippets [underscore|camelcase] Naming convention for generated snippets.
Defaults to underscore.
-v, --version Print version.
-h, --help You're looking at it.
--i18n LANG List keywords for in a particular language
Run with "--i18n help" to see all languages
--junit,OPTION[,OPTION]* Pass the OPTION(s) to the JUnit module.
Use --junit,-h or --junit,--help to print the
options of the JUnit module.
-w, --wip Fail if there are any passing scenarios.
Feature path examples:
Load the files with the extension ".feature"
for the directory
and its sub directories.
/.feature Load the feature file /.feature
from the file system.
classpath:/.feature Load the feature file /.feature
from the classpath.
/.feature:3:9 Load the scenarios on line 3 and line 9 in
the file /.feature.
@/ Parse / for feature paths generated
by the rerun formatter.