Document toolboxDocument toolbox

A new version of Qualitia Automation Studio for Web and Mobile 7.2.x is now available. We highly recommend you upgrade. Find more details here.

Debug Log

The Debug Log provides information about configuration settings, called functions, test execution sequence, action execution details, execution status, and report itinerary.

The Debug Log contains the following details:

Configuration Settings

The Debug Log offers information about the values of the configuration settings that have been configured for Qualitia by you.

Function Details

Functional details provide details of functions called during the execution.

Execution Details

It provides the following details:

Step Itinerary

The Step Itinerary provides information about the step within the test case. It provides information about the following:

  • Suite Name
  • Scenario Name
  • Test Case Name
  • Task Name

Report Itinerary

The Report Itinerary provides information about the components of the tests for which Qualitia has generated the reports. Action Execution Begin At provides the beginning time of the execution.

Action Details

The Action execution details comprise the information about the object and the actions that have been implemented on the object. The details also indicate the status of the implemented actions. The applicable statuses are Passed, Failed, and Defected.

Action Execution Completed At

This provides the completion time of action.

Execution Status

The statuses of the test execution provide information on whether the test cases have cleared the validation test. The execution status helps in identification of application defects and action errors.

The following table describes the execution statuses.

 Execution Status

Description

0

The Execution Status '0' denotes that the test cases have passed the validation test.It indicates that the actual behavior of the application under test is consistent with the expected result.

1

The Execution Status '1' denotes that the test cases have failed.
The various reasons for failure of test case setup are:

  • Error in selection of Action for tasks
  • Error in input parameters
  • Change in object properties
  • Page Sync issue

2

The Execution Status '2' denotes that the test cases have failed due to differences in expected and actual result regarding the behavior of the application under test. It indicates that the application has potential defects related to the functionality under test.

Not finding what you need?