You can check the usage of any CLI command using the inbuilt
e.g. Get help on the options for the
Working with Element locally
Init a local Element project
Init a test script, a default configuration file and a minimal environment to get you started with Flood Element.
Generate a basic test script from a template
Output the test script plan without executing it
Run a test script locally
file: the test script (or path to the test script) to run. Specifies a test script written in TypeScript with a
--chromeSpecify which version of Google Chrome to use. Default: use the puppeteer bundled version.
--no-headlessRun in non-headless mode so that you can see what the browser is doing as it runs the test.
--devtoolsRun in non-headless mode and also open devtools
--no-sandboxDisable the chrome sandbox - advanced option, mostly necessary on linux.
Running the test script:
<file>and rerun the test when it changes.
--ffRun the script in fast-forward: override the actionDelay and stepDelay settings to 1 second in the test script. Specify a number to set a different delay.
--slow-moRun the script in slow-motion: Increase the actionDelay and stepDelay settings in the test script to 10 seconds. Specify a number to set a different delay.
--step-delayOverride stepDelay test script setting
--action-delayOverride actionDelay test script setting
--loop-countOverride the loopCount setting in the test script. This is normally overridden to 1 when running via the cli.
--strictCompile the script in strict mode. This can be helpful in diagnosing problems.
--work-rootSpecify a custom work root. (Default: a directory named after your test script, and at the same location)
--test-data-rootSpecify a custom path to find test data files. (Default: the same directory as the test script)