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.
[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
#Generate a basic test script from a template
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.
#Output the test script plan without executing it
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
#Run a test script locally
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.
--fail-status-codeSpecify an exit code when the test fails. Defaults to 1.
--config-fileSpecify the path to a config file to run the test with. If a path is not specified, defaults to
element.config.js. This flag only works when running a test with a config file
--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)
#Generate a config file from a template
Flood Element supports using a config file across tests within a project. The default config file name (if not specified) is
element.config.js, with the content as below.
#Run a test locally with the default config file
Element will find all the test scripts within the current project that match the
testPathMatch pattern specified in the default config file, then sort the scripts alphabetically (by path-to-script) and execute those scripts sequentially, with the options as specified in the config file.
#Run a test locally with a custom config file
This would be useful in case you want to reuse a config file across different projects.
#Run an Element script on Flood
Since Element 1.3.0, you can launch a flood directly from Element CLI. To do so, you need to be authenticated with Flood first.
#Authenticate with Flood from Element CLI
Visit https://app.flood.io/account/api to get your API Token, then paste it into the above command to get authenticated. Unless you want to change the API Token, this step should be done only once.
#List all Flood projects
#Select a Flood project to use
Every flood needs to belong to a project. Therefore, you need to select a project to use before you can launch a flood.
#Print the current project being used
This command would be useful in case you forgot the Flood project that is being used.
#Launch a flood on hosted grid
--hosted: indicates you're going to run a flood on hosted grid
--vu: number of virtual users to simulate. Default to
500if not specified
--duration: length of the test, measured in minutes. Default to
15minutes if not specified.
--rampup: the amount of time it will take to reach the defined number of
vu, measured in minutes. Default to
0if not specified.
#Launch a flood using on-demand grid
The meaning and default values for
--rampup are the same as launching a flood on hosted grid, which are 500 (users), 15 (minutes) and 0 (minutes) respectively, if they are not specified in the command line.
HOW TO NAVIGATE AND SELECT
After running the command
element run flood, you will be asked to select regions (to run on-demand test), or grids (to run a test on a hosted grid). To navigate among the options, use the Up/Down arrow key. To select an option, press the Space bar. You can select multiple options if you want.