Initiate live testing

Here you will learn on how to successfully launch a live testing session, pitfalls to avoid and why you should avoid them.

Pre-conditions for launching live testing

You must have the following in place:

  1. Project

  2. Robot

  3. Suite: Empty suite, starter suite, Copado’s gitlab, public gitlab and public github

  4. QEditor: It opens up by default for all the above mentioned suites.

  5. A suite must have at least one .robot file for the live testing to even get initiated.

  6. A .robot file with proper configurations for successfully initiating live testing.

Live testing sets up a robot for you to interact with. Therefore, it needs to know the kind of robot and its capabilities to be initialized for you. Hence, live testing is very context specific.

  1. Live testing can only be initiated from a .robot file. You must have a .robot file open in QEditor before you can launch a live testing session.

  2. Almost every time, it is meaningful to launch live testing session from a .robot file containing test cases. The reason being that a test case file imports all the variables, resource files, libraries etc. which is very critical information for a live testing robot.

Launching live testing

Once you are on a .robot file containing test cases, there are a few ways in which you can kick-start your live testing solution.

initiatelivetesting1
  1. From Live Testing quick control on the left

  2. From the Live Testing button on the top right

  3. From Live Testing menu using option (Re)start Live Testing

A live testing session

It takes a few seconds to launch a live testing session. Remember we are setting up a robot for you and configuring it to understand your tests. You will be notified on the browser area when the live testing session is ready.

initiatelivetesting3
  1. A live testing session is active for as long as you are on the live testing tab. The moment you close the editor, the session closes and you will need to re-launch it.

  2. Live testing session times out after 30 mins of inactivity. After which, you will need to re-launch it.