Basics of debugging

  1. To switch to debug mode, click the Debug Mode DebugModeIcon.png or Debug button in Design Studio.
  2. Click [run]  1.png to start debugging.
  3. In Robot view, you can see the state of robot in debug mode. You can check the execution result in the main panel.

    The contents of the [Input / Output] tab are displayed as follows.

    • The [Input] panel displays the input variables.
      Note If the robot does not have input variables, the Input panel will not be displayed.
    • The [Output] panel shows all the values returned during execution.
    • The [API Exceptions] tab shows all API exceptions generated during execution.
    • The [Log] tab shows the logging record that has been written to the log during execution.
    • The [State] tab shows the robot's state.
    • The [Summary] panel (right side of the main panel) shows a summary of the process, including the number of Return Values, API exceptions and HTTP requests. Also the amount of data sent and received, and the number of JavaScript instructions executed.
    Note It is important to understand that the execution of debug mode and design mode in Design Studio are separate. Therefore, debug mode has its own current step and robot state, which are different from design mode's current step and robot state. In debug mode, current step refers to the steps you are trying to perform or being executed, and robot state refers to the input of those steps.
  4. Click [stop]  8.png to stop debugging.

    You can stop debugging at any time.

  5. To stop debugging when a specific problem occurs, enter the [Stop When] action.

    You can choose to stop debugging when values are returned (Return Value), an API exception is reported, or a breakpoint is reached.
    Of course, the system will stop debugging when the robot's execution is complete.
    After finishing debugging, the status bar at the bottom of robot editor shows the reason for the stop.

    If the robot terminates debugging before robot execution is complete, you can check the current robot status on the [State] tab. The [Variables], [Windows], [Cookies], and [Authentications] subtabs display the robot state as the state view in Design Studio. If execution stops because an API exception is reported, the API exception will be displayed in the [API Exceptions] subtab.

  6. If the robot stops debugging before robot execution is complete, click [run]  1.png to resume debugging.

    You can restart debugging if you click [restart debug] 7.png. The current debugging process will stop and the debugger will be ready to start a new one when the robot is launched.

    Note Whenever you change the current robot in Design Studio or replace it with another robot, debugging will automatically restart.
  7. If your robot has variables need to be input, you can edit them in the Input panel. Press Enter to restart debugging with the new input variables.

    You can not edit input variables while debugging is in progress. You must restart debugging if you want to change the input variables.

0 out of 1 found this helpful



Article is closed for comments.