Execute
Executing the CLI version of marathon requires you to provide all the options through the Marathonfile. By default, it will be searched in the working directory by the name Marathonfile.
If you need a custom file path you can specify it via the options.
foo@bar $ marathon -h
usage: marathon [-h] [--marathonfile MARATHONFILE]
optional arguments:
-h, --help show this help message and exit
--marathonfile MARATHONFILE, marathonfile file path
-m MARATHONFILE
Marathon CLI supports the following commands: run, parse and version.
Run command
foo@bar $ marathon run -h
Usage: marathon run [OPTIONS]
Run Marathon to execute tests
Options:
-m, --marathonfile PATH Marathonfile file path
--analyticsTracking VALUE Enable/Disable anonymous analytics tracking
--bugsnag VALUE Enable/Disable anonymous crash reporting. Enabled by default
-h, --help Show this message and exit
Parse command
foo@bar $ marathon parse -h
Usage: marathon parse [<options>]
Print the list of tests without executing them
Options:
-m, --marathonfile=<path> Marathonfile file path
-o, --output=<text> Output file name in yaml format
-f, --include-flaky-tests=<value>
Include/exclude flaky tests that will have
preventive retries according to the current
flakinessStrategy
-h, --help Show this message and exit
Version command
foo@bar $ marathon version -h
Usage: marathon version [OPTIONS]
Print version and exit
Options:
-h, --help Show this message and exit
Default command
Default command is the run command, so the old CLI syntax works the same way:
foo@bar $ marathon -m MARATHONFILE