Skip to end of metadata
Go to start of metadata

Once a test suite finishes its execution, a historical report will be automatically generated and stored in Reports. 

For example:

The report will be named with following the naming convention: YYYYMMDD_HHmmss, which is the datetime when the test suite starts its execution.

Report Overview

In Test Explorer view, double-click on a historical execution of a test suite to view its details:

where:

ComponentDescription
Test Cases TableList of executed test cases.
SummarySummary information of executed environment.
Execution Settings

Settings of executed browsers/devices. For example:

Execution Environment

Other information about the executed system. For example:

 

Test Cases List

  • The summary information of all executed iterations done in the test suite is displayed here. Each time when a test case is executed with a test data row is considered an iteration.
  • Users can easily determine which type of information to be displayed by using the provided filters:

    Filter

    Description

    Passed

    Show only iterations which are passed.

    Failed

    Show only iterations which are failed.

    Error

    Show only iterations having errors.

    IncompleteShow only incomplete iterations
  • By selecting an iteration in Test Case Table and click Show Test Case Details, you can view details regarding its executed logs.
  • If qTest and JIRA are configured in project settings, you can submit data to those systems. Refer to qTest Integration and JIRA Integration for more details.

 

Test Suite Summary

This section gives the summary information of the test suite:

where:

FieldDescription
Test Suite IDThe ID of the executed test suite in Katalon Studio.

Hostname / OS / Platform

The environment where the test suite was executed

Start / End / Elapse

Execution start/end date time and duration
Total TCTotal number of test cases, along with their executed status.

 

Test Logs Details

This section shows all information regarding the iteration selected in the Test Cases Table section.

Test Log Tab

  • Details regarding all the executed steps and their status are displayed in this tab. 

    where:

    ComponentDescription
    Log InformationInformation of the test step selected in the Test Case’s Log section:
    • The Name of the test step (the name of the keyword used in the test step)
    • Execution Start/End date time and duration
    • The Description of the test step
    • Any system Message raised when the test step was executed
    Log Image

    The screenshot taken from the application under test, it is captured in either of following situations:

  • Users can easily determine which type of information to be displayed by using the provided filters:

    Filter

    Description

    Info

    Show the messages logged for information/reference.

    Passed

    Show the steps which are successfully executed.

    Failed

    Show the steps which are failed to execute.

    Error

    Show the steps having errors.

    IncompleteShow incomplete steps due to other factors such as wrong syntax, power shortage, disconnected network, etc...
    WarningShow the steps which have warning status.
    Not RunShow the skipped steps.
  • If JIRA is configured in project settings, you can submit a ticket to this system. Refer to JIRA Integration for more details.
  • Screenshots are taken for the failed steps and you can hover the mouse cursor over the attachment icon to review. 

Information Tab

Users can find the summary information of the test case in this tab.

where:

FieldDescription
Test Case IDThe ID of the executed test case in Katalon Studio.

Start / End / Elapse

Execution start/end date time and duration.
DescriptionThe description of the test case.
MessageAny system message raised when this iteration was executed.

Integration Tab

The information regarding qTest Integration of this iteration is displayed in this tab.

where:

FieldDescription
Test Log IDThe ID of the integrated qTest Test Run.
Test Run AliasThe alias of the integrated qTest Test Run.
AttachmentIndicate whether all the execution log and report are placed in a zipped file which is sent to qTest as an attachment.

Export to other formats

For the purpose of sharing, users can generate reports of test suites into other formats such as HTML, CSV, PDF and JUnit using the context menu in Test Explorer as example below: 

  • No labels
Write a comment…