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 screenEditor.

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 When checked, the execution will pause if there is a pauses upon failure.

   • Go to Line: If Allows you want to go navigate to any particular a specific step , by inserting entering the number of the step, you can directly go to that stepstep number.

   • 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 Lets you jump to a selected step during test case execution.

   • Expand All: This will expand Expands all the steps.

   • Collapse All: This will collapse Collapses all the steps.

   • Refresh: Updates the script if changes are made by other users. A red dot appears near the Refresh button to indicate updates.
     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 Starts executing the script in the browser. This button changes to Pause during execution, then to Continue after pausing, allowing you to resume the test case.

   • Stop: Stops the execution.

   • Next: This will help you with Enables line-by-line execution. You need to After each step, click this button after every step to proceed. To continue the normal execution . Suppose after two steps you want to continue with direct execution, you can click Continue to run the entire scriptafter stepping through some lines, click Continue.

4. Click Exit Debugger to exit the debugger.

Modifying Steps

While debugging test cases, there can be instances where you may want to change modify the parameters or object details such as (e.g., locator type/value and so on). The Modify step functionality provides facility to do so when debugging the test case. This feature is most useful when you want to check the impact of a certain parameters' data change or an object locator type/value change or a conditional expression change on Step functionality allows this during test case execution, especially for testing how changes to parameters, object locators, or conditional expressions affect the test case.

• Double-click the step under execution to launch the Modify Step dialog. This loads the selected step information in the dialog box.

• Only

...

• steps currently under execution can be modified.

All the debugger operations are applicable to the tasks and test cases that are shared for Design Updates.

...

• In a step, you can modify the following:

  • Edit an An object’s locator type and value.

  • Change static Static and variable parameters.

  • Edit the conditional Conditional expression.

• However, these changes cannot be Changes made to object locators are saved in the test case. Only modification in Object’s locator type & value directly get applied in the Object toolkit. The other changes will get permanently applied in TC through Change logObject Toolkit, but changes to parameters or conditions must be applied manually using the Change Log.

• When debugging a test suite of a desktop project, you cannot edit an OR object.  

...

To modify parameters of a step:

1. Right-click on the parameter and select Modify Data to edit the parameter.

2. Selecting Modify Data will open the Modify Data window.

3. Change the value and click Save to continue; otherwise, Discard.

Modify operation on a step only allows modifying the parameters of that step (if any). The modified parameters can only have static/literal data. The modification of data is only applicable to that particular Changes to parameters are limited to the current task iteration for a task step and only for that TC -level step, or to the current test case iteration for a TC test case-level step. The change of parameter’s data does not get propagated to subsequent Task and TC Modifications do not propagate to subsequent iterations.

Modifying Objects of Step

Qualitia users You can modify object's locator type and value of an existing step. The modified object  Changes will reflect in all the subsequent instances of the objects wherever it is used in object within the test case. In case of Desktop’s DP object, you can add/edit/remove property type & value.

To modify an object of a step:

1. Right-click on the object and select Modify Objectto edit the Locator Type and Locator Value.

2. Selecting Modify Object will open the Modify Object window.

3. On the window, change the Locator Type from the dropdown menu and add the Locator Value. Click Save to continue; otherwise, click Discard.

...

You can modify conditional structure using modify step functionality of debugger. For conditional structure, we can only modify the if If condition expression.

To modify the condition structure:

1. Right-click on the If condition expression and select Modify Conditionto modify the condition.

2. Selecting Modify Condition will open the Modify Expression window.

3. Change values for In the Modify Expression window, change the values of the If condition and click Save to continue; otherwise, click Discard.

View Test Case Information Per Test Case Iteration

The debugger view loads the Debugger displays test case information per test case iteration. The test case iteration number can be selected from the drop-down at the left-top corner of the debugger window.  The status of the test case iteration execution is updated along with the test case iteration number. Only a step that is under execution is allowed to be edited during debugging, no other steps can be modified. for each iteration, and you can select the iteration number from the dropdown at the top-left corner of the Debugger window. The status of each iteration is updated accordingly. Only steps under execution can be edited during debugging.

The debugger view allows you navigating through all executed and unexecuted TC test case and Task task iterations before the debugging starts, while the test case is either waiting on a break-pointbreakpoint, being debugged step by step, or has finished execution.  

The Details tab also displays the test case iteration number in addition to other detailed information of each step being executed during the test case. 

View Task Step Details by Task Iteration

You can view the task-level details of each respective task iteration. This can be done before test case debugging starts, while the debugger is waiting at some break-point, when doing step by paused at a breakpoint, during step-by-step debugging using "Next" (F6), or after the test case execution is complete.

You can view the TC level test case iteration details by changing the TC iterations from the Test case iteration Case Iteration list. You can also view the Task iterations task iteration details by selecting appropriate task iteration number from the task iteration list which is present along with , located next to the task header at the start of every each task.

...

Details

The Detail Details tab provides the execution details of every step. The Object, Action, Parameters, including the object, action, parameters, and the test step execution result is shown in the Detail tab. You will also get the see a snapshot of the browser, which can be downloaded. From Settings, you can enable the setting s to get either the choose whether to capture a browser screenshot or the a desktop screenshot.

Change Log

Information about any modified steps is logged in the The Change Log section . The change log view shows all the changes that have been logs any modifications made to test steps step parameters or conditional structures, except for the objectsexcluding object changes. The change log for a debugged test case is maintained till any until another test case is debugged again.

1. The changes are not applied directly applied in the Test Case. You have to select a log by checking a check box and to the test case. To apply them, select the log entry by checking the checkbox, then click Apply Changes from the top-right corner of the screen to apply those changes to your test case.

2. Clicking Apply Changes will open a window confirmation window Apply Changes. Click Confirm to continue; otherwise, click Discardapply the changes, or Discard to cancel.

3. Once you click Confirm, the Test Case test case will be saved, and all the functions on the Change Log screen will be disabled.

...