Command line interface¶
A Robot Framework frontend script. All command line options are passed to pybot/jybot, except for ones listed below.
It adds ./libraries and ./resources to PYTHONPATH so that libraries and resources can easily be imported in test cases. Additionally, it will recursively search the ./testcases directory for any subdirectories named “libraries” or “resources” and add those to PYTHONPATH.
Use rfcli –help to see pybot/jybot help.
usage: rfcli [RFCLI OPTIONS] [PYBOT OPTIONS AND ARGUMENTS]
Named Arguments¶
--version | show program’s version number and exit |
--rfcli-output | Output directory. (default: $HOME/public_html/rfcli/, if exists, otherwise ./rfcli_output/ |
--rfcli-help | Show help for wrapper command Default: False |
--rfcli-debug | Toggle debug for wrapper command Default: False |
--rfcli-show | Show pybot/jybot command that would be executed, but don’t execute it. Default: False |
-j, --jybot | Use jybot instead of pybot Default: False |
-t, --target | Target files can use either INI or YAML formats. Target can be specified in two ways: (1) Name of the target system without any extension. Corresponding “<target>.ini” or “<target>.yaml” file must exist under “targets” directory. (2) <target>.<extension> file with absolute or relative
“.ini” or “.yaml”. More than one target system can be specified. Name of the first target will be exported to Robot variable RFCLI_TARGET_1, second to RFCLI_TARGET_2 and so on. Target properties are read from the INI file and available as Robot variables {RFCLI_TARGET_1.IP}, {RFCLI_TARGET_1.USER} etc… Target properties in the YAML file can be in a nested structure. The properties are read from the file. Each property name is prefixed by the names of each level of nesting leading to it and separated by “.”. The properties are available as Robot variables {RFCLI_TARGET_1.ENV.PARAMETERS.EXTERNAL_NETWORKS.EXT0}, {RFCLI_TARGET_1.ENV_PARAMETERS.NTP_SERVERS}, etc… |
--rfcli-no-pythonpath | |
Do not set PYTHONPATH to libraries. Default: False |