Adding a robot

We have moved

This is a legacy version of Copado Robotic Testing help. This page will not be updated anymore.

See for up-to-date documentation.

By clicking on Add a robot button Add robot dialog box pops up, shown as below


Description for adding a robot

  1. Robot name: A Robot must have a name, please enter any name which suits your/robot's purpose.

  2. Robot description: A Robot must have a description. You can think of description as a purpose for the Robot.

  3. Run Environment: If you are deploying a full-fledged cloud based robotic software testing solution, all your robots would run in cloud environment. A static / QConnect run environment is needed if your system under test exists in a closed intranet and is not accessible through cloud or if you need to connect to a physical device etc. However, for the purpose of this document, we will restrict ourselves to cloud environment.

  4. Robot Type: This option lets you choose the platform on which your application is hosted. A web robot is used for testing web applications, should you wish to test a mobile application in a cloud device farm, you could select BrowserStack or BitBar service providers. Should you have an existing account you can configure them by yourselves, should you not have an account with any of the service provider, Copado or the suppliers can assist you with getting one.

    1. Bitbar: Configuring Bitbar would require you to have an Api Key. robotsaddingBB robotsaddingBB credentials

    2. BrowserStack: Configuring BS would require you to have a username and access key. Note that these are not the same credentials you use to login to BrowserStack web page. You can find username and access key from BrowserStack / Profile / Settings section. robotsaddingBS robotsaddingBS credentials

  5. Variable: You can pass variable values to the test script. For instance, the following setting would define the BROWSER variable to be set to Firefox. Any variable defined at a robot level is available for all the suites under that specific robot. Like before, variables defined here could be marked as secret. A typical example for robot level secret variable would be robot's identity, username and password. robotsaddingvariable

  6. Execution parameter: You can change the default values by setting execution parameters that control how test cases are executed and what outputs are generated. You can pass them to the test runner so that Name presents the option and value its value. For a list of useful execution parameters check the appendix. For instance, this option set the values for -L option: robotsaddingcommand