...

Qualitia test case development view allows you to perform following operations related to the debugger:

...

1. Add or  or Remove the  the break-point at any step of test case by clicking on the line numbernumbers.
   You can add/remove the breakpoints on debugger view the Debugger windows as well.
2. You can Clear All Breakpoints right-click step(s) of the same type i.e. only TC steps or only Task steps or only Task and click on Skip / Unskip to Skip or Unskip steps from execution/debugging. clicking the step with a single click.
   
3. Skip / Unskip the steps from executing / debugging right-clicking the step.  
   For more information about the Skip functionality, refer to the Skip feature documentation.
4. You can right-click and click Clear All Breakpoints to remove all breakpoints which you have applied on the test steps on the same view.
5. Click Shift the focus to any line number of the test case using the Go To button to shift focus to the desired line number on the Test Cases screen.To launch the debugger click on . 
6. Launch the debugger window clicking the Start button. This will launch a new debugging session for the selected test case.
7. To view the last test case debugging logs and details click on the Log button.

...

1.  
2. View the detailed debugging logs of the last test cases clicking the Log button.

Start Debugger

Once you have added all the required break-points, you can start debugging test case. 

1. Click the Start button to start debugging the current test cases. 
    During debugging test case, the development view is not available for editing.

...

1. Click the Stop button when you want to stop

...

1. /pause the execution of selected test case. 
   This will still keep the debugger window open. You can directly close the debugger window as well which will stop

...

1. debugging of the test case

...

1. .
2. Click the Log button in Qualitia Automation Studio to view the detailed logs of the last executed test case.
    The option to stop the debugging at any point in time is only available when you are debugging using F6 / Next command (

...

1. Image Added) or currently waiting at

...

1. the break-point.