...
1- In order to test and debug a test case you have written, click Download Local Player button under your username.
Alternatively, you can directly navigate to the test case you want to run and click Play.
...
2- As the Test Case is running, it will update the status of each step in the Status field shown below by providing (pass, fail, or fail_skip). The overall status is shown in the bottom left corner of the screen in addition to the execution time.
3- When a test case is run locally, a watch window (Variables) will appear on the right side of the screen that shows all of the variables and their values as test case is executing. The following is a list of system variables:
...
You can drag and drop any variable on the watch window to your convenience as long as the test case execution is paused/finished. The below is an example that shows dragging and dropping variables.
4- As your test case is running, the play button will be greyed out while the pause and stop buttons will active. In the middle of execution of a test case, you can click the pause button to pause the execution. Now, you can click on the play button anytime you like to resume the execution. While test case is paused, you can make changes to the test case, save your changes, and resume the execution.
5- When in pause status or when the test case has been executed to the end, you can click on the test case step number to set the cursor to the step you would like to re-execute (the arrow next to the step will turn green when you click it). You can simply hit the play button to resume your test case from where the green step is.
6- At any time during the execution of a test and after you hit the pause button, you can edit the test case to resolve the error(s) encountered during your local test run or make any modifications, then click on the step number that you just fixed to run it again, and hit the play button. You can repeat the above steps until you have a working Test Case.
7- When your Test Case execution is completed, you can hit stop to reset your player. This will in turn close the browser that was launched earlier as well as the watch window (Variables) on the right side.
| Info | ||
|---|---|---|
| ||
In case timestamp field in data templates is checked, clicking Stop will refresh the timestamp on your local run. |
...
8- You can also put breakpoints in your test case by clicking on a checkbox under Break next to the step which changes the color of the step to red. When you execute the test case, it will stop at the break point automatically. Your breakpoints will be saved when you save your test case.
9- In case you are executing a test case and need to make changes to specific steps before continuing, step over feature makes it easy for you to debug your test case step. Add a break-point at the step where you need the execution to stop, or play your test case and pause wherever you like.
10- When the break-point is reached or test case is paused, click Step Over button to play the unexecuted step.
11- Once the step is played, the execution will pause again until you decide what to do next.
12- You can keep using Step Over to see what execution does. In case of errors or unexpected actions, you can do any debugging to the steps before continuing. Once finished debugging, you can click Play to resume from the last location or select a step to continue executing from there.
...