Qualitia Automation Studio (QAS) provides an easy-to-use interface for you to develop developing test cases. The QAS Debugger allows helps you to understand the course of test case execution and change it if required, without re-executing entire test case every time you made any changes to itchanges are made.

When developing test cases in Qualitia, you can verify whether if it works as expected without running it end-to-end. A test Test case execution once initiated can be paused in between, or it can be modified mid-way or modified during execution. So if you come across any fatal error that is failing your test case due to certain If you encounter a fatal error due to a specific step or data at in a given TCtest case/Task task iteration, you can modify the test case when the while execution focus is focuses on a that step.

Additionally, it allows to the QAS Debugger helps you understand the number of TC test case and task iterations applicable on to a test case and visualize the data associated with different steps for across different task and TC test case iterations.

Key Features of QAS Debugger

The Qualitia Debugger provides an in-depth offers a comprehensive test case debugging experience to the testers along with the following facilitiesfeatures:

1. Debug and execute test case cases step by step.

2. Pause execution at the point of failure point. You can also pause the test case execution at any step using break-point facility. These facilities could be utilized for reaching and analyzing breakpoint feature, allowing you to reach and analyze the point of failure without having to execute fully executing the test case entirely or single stepping entire test case.

3. Modify test stepsteps, its parameters, and its object details while during debugging test cases.

4. Comprehensive and A user-intuitive interface for you to see various TC and Task iterations and their friendly interface displaying test case and task iteration details.

5. Highlight any step in the test case using its line number.

Execution

Launching the Debugger

To debug a test case:

1. Once , the test case and the script are ready to execute, click Execute from the top menu of the Test Case editor Editor screen.

2. Clicking Execute will open the Debugger screen.

3. On the Debugger screen, you will see a tool bar with the toolbar offers the following options:

   • TC Iteration: Here, you can select the number of TC iterations from the dropdown. This will be in is read-only mode and you can only check displays the values of the other iterations here.

   • Pause On Failure: If this is checked, the execution will pause if there is a pauses upon failure.

   • Go to Line: If you want to go to any particular step, by inserting the number of the step, you can directly go to that step.

   • Jump to Selection: While executing the test cases, if you want to go to the selected step, clicking on Jume to Selection will take you to that step.

   • Expand All: This will expand all the steps.

   • Collapse All: This will collapse all the steps.

   • Refresh: If multiple users are working on the script, and one of the users update the test case or task you will see a Red Dot near the Refresh button. The Red dot indicates update in the Test Case or the task. Click Refresh if you want to incorporate those changes in your script else continue.

   • Execute: The browser will execute the script, when you click Execute. Once executed, this button will then be used to Pause the execution. After pausing, it will be transformed into Continue button. By clinking Continue you can restart the execution. So, the single button will perform Play, Pause, and Continue.

   • Stop: This can be used to stop the execution.

   • Next: This will help you with line-by-line execution. You need to click this button after every step to continue the execution. Suppose after two steps you want to continue with direct execution, you can click Continue to run the entire script.

4. Click Exit Debugger to exit the debugger.

...