Posted on

Jumps with Sub-Return function

For actions which needs to be recurrently run several times throughout the test (e.g. switching users) you can use Jump with Sub-Return function.

With JUMP #sub:tagName you set the base of the following jump session.
The command makes you jump to the TAG #sub:tagName.
With the JUMP #return:tagName you jump back to the place where you started (set the baseline).



… some more actions …


…some recurrent actions…

Posted on

How to use Branching

If you need to create the same test for your product multiple times due to minor differences of different settings (e.g. language, browser, environment, etc.), you can use Branching. This function allows to record test steps for all settings under test in just one test case.

Create a first branch

First, you need to create a branch in your predecessor test.

  1. Create a test and record actions in one of your chosen browsers (e.g. Firefox, Chrome, etc).
  2. In the mode create a new variable by clicking .
  3. Name your variable BRANCH using upper case and insert the value according to the current browser (e.g. Firefox).
  4. Click .

Create a second branch

Then create a second branch in your successor test.

  1. Create a new test as a successor and choose in the test settings your previously created predecessor.
  2. In the mode click on the overwrite symbol to the right of your BRANCH variable and insert the new value for your second branch (i.e. Chrome).
  3. Play your test until the step where the branching should start.
  4. Go to mode and enter your variable for the first browser in the field “branch selector” (e.g. Firefox).
  5. Jump to the next step using in the menu of the following step.
  6. Click on “Insert action” and record the first action of your second branch (e.g. double click on Chrome browser). The step will be automatically marked with the name of your second branch.
  7. If the next action of your test is different in the second setting, repeat steps 4 – 6.
  8. If it is the same, simply play the following steps one by one until the action is different again and repeat steps 4 – 6.

In order to run both branches in one schedule, simply create a second successor test and name it according to your first branch.