You can check the usage of any CLI command using the inbuilt
e.g. Get help on the options for the
Init a test script, a default configuration file and a minimal environment to get you started with Flood Element.
[dir](string) the directory to initialize with an Element test script. Defaults to the current directory.
--skip-install(boolean) Skip yarn/npm install. Defaults to
file(string) the test script name to generate. Specify a file name with a
.tsextension (TypeScript), for example,
You should make sure that
package.json file in the project root folder has the attribute
name before running this command.
file(string) the test script (or path to the test script) to output the plan from. Specify a test script written in TypeScript with a
--json(boolean) Output the test plan as JSON format. Defaults to
file(string) the test script (or path to the test script) to run. Specify a test script written in TypeScript with a
--chromeSpecify which version of Google Chrome to use. Default: use the puppeteer bundled version. Change it to
'stable'to use the Chrome version installed on your system, or provide a path to use Chrome at the given path.
--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
--strictCompile the script in strict mode. This can be helpful in diagnosing problems.
--work-rootSpecify a custom work root to save the test results. (Default: a directory named after your test script, under /tmp/element-results of your project folder)
--test-data-rootSpecify a custom path to find test data files. (Default: the same directory as the test script)