Adding dependencies to Robots, pre & post-processing

Most of the times you would not need to configure anything to the Robots in Qentinel Pace for executing your test cases. However, in RPA cases or custom libraries, you may need to install certain dependencies to the Robots. You may also have a need to run specific commands before or after the run itself. You can achieve this as follows:

Installing dependencies

Add a file requirements.txt in the root of your repo. Robots in Qentinel Pace will run command pip install requirements.txt before suite is run and install all the dependencies mentioned in that file. A common use case for this that Qentinel Pace does not have a certain Python package or Robot FW library installed by default.

The requirement.txt should at minimum define each package to install in it’s own line. You can also specify certain versions.

requirements file
Figure 1. requirement.txt example file in Pace Editor
Example of specifying packages with or without version:
####### example: requirements.txt #######
###### Packages without Version Specifiers ######
beautifulsoup4
requests
###### Packages with Version Specifiers ######
#   See https://www.python.org/dev/peps/pep-0440/#version-specifiers
docopt == 0.6.1             # Version Matching. Must be version 0.6.1
keyring >= 4.1.1            # Minimum version 4.1.1
coverage != 3.5             # Version Exclusion. Anything except this version

Pre & Post-processing

Add a file pace.before in the root of your repo. All the commands mentioned in pace.before will be run prior to suite run. Ìf you need Robots to execute a set of commands after suite run, you will need to add pace.after file in the root of your repo.

The file is run like a source in the current shell (. File), so it can have any command that works in shell.