Header

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Installation Process for Reports and Dashboards Portal

You can either enable this dashboard functionality while installing/upgrading Qualitia Server or you can do it after you complete the installation or upgrade process. 

Qualitia consumes an additional database (except master and project databases) for managing data related to the dashboard functionality.

To enable Reports and Dashboards Portal:

  1. Log on to the machine where you have installed Qualitia Server. 
  2. Double-click the Qualitia Automation Studio Server icon.
    The Welcome to Qualitia Setup Wizard screen appears.
  3. Click Next.
    The Database Server Details screen appears.



  4. Click Next.
  5. Select Enable Dashboard option and enter the desired name for the dashboard database.



  6. Click Next and then click Install.
    Now you can access dashboards from the Dashboard section of Qualitia Automation Studio clients or using the dashboard URL on using any browser on any machine in the network.

Reports and Dashboard Portal URL contains the Hostname/IP:Port from the machine where Qualitia server is installed followed by the login page URL, that is, qualitia/sign-in. By default, system uses port number 8887 which users can change while installing Qualitia server.

The sample URL may look like:

You need to login and the landing screen contains the options to navigate to Web Dashboards, Real-time reporting or Server Administration portals, depending upon your user role in Qualitia.

Getting Started with Reports and Dashboards Portal

Prerequisites

Browser NameVersion
Google Chrome73 to 75
Mozilla Firefox66 and 67
Microsoft Edge44
Chromium 77
Safari12
Internet Explorer

10 and 11

  • Access to Qualitia Server machine and port 8887:

Accessing Web-Based Dashboards

Last Updated

Dashboard Refresh Interval

Important Notes:

You can view the data of last 30 days for a project in the dashboard. You can filter the test execution dates from the filter given at the top of the screen. You can also filter the data based on other filters such as project, suite and so forth.

To view the detailed information about any bar/line from the chart, hover your mouse pointer over that bar/line.

If a test case is executed multiple times in a selected time frame, multiple occurrences are counted while loading the metrics and charts.

If there is no data present for the selected filter criteria, you will see a message in the widget that there is no data to display.

Dashboards


  • For test suites executions on desktop projects, the following charts are not displayed:
    • Test Execution Results Trend
    • Execution Trend on Web
    • Execution Trend on Mobile
    • Test Execution Trend for Both (Mobile & Web Executions)
    • Failures by Browser
    • Failures by Operating System
  • Web Dashboards display the suite execution results as per the time zone of the QAS server.

Automation Test Progress Report

  • Tests Executed: Displays the total number of test cases that have been executed.
  • Total Pass: Displays the total number of passed test cases.
  • Total Fail: Displays the total number of failed test cases.
  • Total Defects: Displays the total number of test cases that have defects.
  • Tests Not Executed: Displays the total number of test cases that are marked for execution but did not get executed due to one reason or another.

Real Time Reporting Portal

Introduction

  • Through a Qualitia Client: It directly displays Suite of Suites Screen .
  • Through an Offline Suite: It displays the login screen if the offline suite used is present on your machine and configured with the Qualitia Server. Ensure that you have access to the associated project to track the test suite execution progress. 

Real Time Reporting shows the reports of test cases executed through a TFS/Azure DevOps pipeline only after the pipeline execution is completed.

Real Time Reporting Portal does not support test cases executed through HP ALM.

Accessing Real Time Reporting Portal

Pre-Requisites

  • Enable the Real Time Reporting checkbox in the mapped execution profile or Systems Execution Profile Settings.

  • The Real Time Reporting Server has enough drive space to displays test suite results. For more information, refer to Server Space Notification.

  • For an offline suite execution, your computer is connected to Qualitia Server. Also, you need to specify the Qualitia Server URL in the Settings tab of Qualitia Offline Configuration Manager

Additional Configurations for Log Files

SettingsDescription
Enable Real-Time ReportingDisplays the test execution results in the Real Time Reporting Portal. Also, if Web Dashboards feature is enabled, you can view these records in the Dashboard portal.

Maximum Size Per Log File

Lets you specify the maximum size for every log file of a test suite execution. The default value is 1MB.

Application Step Log Size

Lets you specify the maximum size for logs of a step. The default value is 1MB and the maximum value you can define is 2MB.

Application Log Level Generates Info Logs, Error Logs, or All Logs for the test suite executions. You can select None, if you do not want any.

Suite of Suites Screen

  • Test Suite Environment Details

    • Shows the test suite name, machine name, IP address, and project name.

    • Qualitia denotes the test suite execution is through a Qualitia Client and Offline denotes the offline suite execution either as a standalone or using a Continuous Integration tool.

    • Mouseover on the Environment Icon to view the operating system and browsers used for test case execution.

  • The total execution duration
  • Test Suite Execution Details

    • The total number of test cases, with details of the number of test cases that passed, failed, have defects, and are not executed. It also shows a progress chart with the completion percentage for the executions in the process.

  • Realtime Reporting Portal displays the execution results as per the local time of your computer.
  • If the execution progress for a suite execution shows a red dot, it indicates that the suite execution results are not updated from the last 5 minutes. You need to check whether the test suite execution is in progress or the connection to Qualitia server is lost.
    Real Time Reporting portal marks the suite execution results as Aborted when they are not updated for more than 1 hour. For more information, refer to Aborted Test Suite Executions.

Server Space Notifications

  • 10% to 30%: A warning message in amber appears at the top of the Portal page, which indicates the amount of drive space available along with the percentage. You must monitor the drive space and ensure that it does not reduce to less than 10%.

  • Less than 10%: A warning message in red appears at the top, which indicates that Real Time Reporting cannot display information on new suite executions. Also, you cannot upload or save a report.

Filtering a Test Suite List

  • Select a date range or click the Filter button in the top-right corner.

  • Select the appropriate options from the list of filters.

Uploading a Test Suite Execution Summary Report

  • During the execution, the results are not pushed to the Real Time Reporting Portal due to network failure or the services of Qualitia Server restarted
  • An offline suite execution was not connected with Qualitia Server
  • A test suite execution was not configured to display its results on the Real Time Reporting portal
  • A test suite executed through parallel execution using Power Shell Utility
  1. Create a ZIP file of the report folder that you want to upload.
  2. Open the Suite of Suites screen.
  3. Click the Upload button placed at the top-right corner.
  4. Drag the ZIP file of the report or browse to upload the ZIP file of the locally saved test suite execution report.

Test Suite Execution Summary Report 

Report ElementDescription
Status Icon

Indicates the number of test case iterations that have failed and have defects along with the total number of test case iterations.

Also, a refresh icon denotes the relevant test case iteration execution that is in progress. 

If the current project is integrated with a defect management system, then for defects logged automatically or manually, it displays a bug icon. Upon hovering on the bug icon, all the associated defect IDs along with their links are displayed. Also, it shows whether the defect is logged automatically.

Test Case ElementIndicates the test case name or a test case iteration number.
ModuleIndicates the associated module name.
EpicIndicates the associated epic name.
Story Indicates the associated story name.
Scenario Indicates the associated Test Scenario name.
Manual TC Id Indicates the associated Manual TC Id.

The execution time for the suites executed on desktop applications does not count the time spent on launching UFT. 

The Module, Epic, and Story columns appear only if the associated project of the test suite is integrated with a Qualitia Design Studio project.

  • If the test suite execution is in progress, a blue-sticky status bar appears at the bottom of the screen, which shows the following details of the test case:

    • The test case name

    • The iteration number in progress and the total number of iterations

    • A timer shows the amount of time lapsed since execution

Filtering the Test Suite Execution Summary Report

  1. Click the Filter button.

  2. Select the appropriate filters.

Exporting the Test Suite Execution Summary Report 

  • Click three dots, and select Export to Excel. 

Sharing the Test Suite Execution Summary Report

  1. Click three dots, and select Share Link.
  2. Click Copy to copy the link.

Wrapping up the Test Suite Execution Summary Report

Customizing the Test Suite Execution Summary Report

  • Click three dots, and select Table Config to show or hide the columns.

Saving the Test Suite Execution Summary Report

  1. Click three dots, and select Save As Report.
    The report is saved in the Download folder, which is specified in the browser's settings.

Logging a Defect Manually in the Integrated Defect Management System

Test Case Iteration Detailed Report 

  • The execution duration along with the start and end time

  • The number of steps that have failed or have defects along with the total number of steps 

  • The number of tasks that have failed or have defects along with the total number of tasks  

  • The execution duration along with the start and end time.
  • The total number of test cases, with details of the number of test cases that passed, failed, have defects, and are not executed. Also, a pie-chart shows the test case count per status for the test suite.
Report ElementDescription
NoIndicates the step number.
Status Icon

Indicates the execution status of the step.

If the current project is integrated with a defect management system, then for defects logged automatically or manually, it displays a bug icon. You can click the defect id links to view the defects in the associated defect management system. Also, you can know the defects that are auto-created.

Test Case Element

Indicates one of the following test case elements:

  • Iteration number
  • Task name
  • Condition type
  • Step name, which indicates the action performed.
    If a step contains results for an API response or generic actions such as CompareTabularResults, you can view those results in the associated info logs.
Data Indicates the data associated with the action.
Object Indicates the object name.
Execution Time 

Indicates the execution time as per the associated hierarchy type.

Filtering the Test Case Iteration Detailed Report 

  • Click the Filter button.

  • Select the appropriate options from the list of filters.

Wrapping up the Test Case Iteration Detailed Report

Navigating through the Steps and Tasks

  1. Select an appropriate step and click the Screenshot and Log icon. The screenshot and the log appears.

  2. You can enlarge a screenshot and navigate across the screenshots of the next or previous steps.

  3. The Info Log section shows the following details:
    1. Step Itinerary : Indicates the task, test case, scenario, and suite name.
    2. Message: Describes how the step was executed. If the step has failed, it shows the reason of failure. 
       If the step contains the results for an API response or generic actions, it contains a link that opens the results.
      You can view the results in the following formats:
      • json
      • xls
      • js (used for opening XML files)
    3. Additional Messages: Indicates the name of the action, its execution Start and End time, and associated message received from the engine. If it contains the additional message, click the + symbol to see the additional messages. 

    4. Execution Status: Indicates the execution status of the step as an integer.
      1. 0 denotes the step has passed.
      2. 1 denotes the step has failed.
      3. 2 denotes the step has a defect. 
  4. The Error Log section shows if any exception occurred in execution.
  5. The Configuration section shows the configured settings used for the execution.  

Aborted Test Suite Executions  

  • If the user terminates the test suite execution forcefully
  • If the Qualitia Client or offline execution crashes
  • If the Qualitia Server services restart
  • If the Qualitia Server loses its connection with the Qualitia Client or Offline Package due to network failure
In case of network failure scenarios, if the connectivity resumes before the test suite execution completes, then its results are displayed. As per the execution status, the test suite execution is displayed on the Completed or Aborted tab.

Viewing an Aborted Test Suite Execution Summary Report

Viewing a Failure Summary

Failure categorization are not available for desktop projects.

The following table shows the pre-defined failure categories:
Failure CategoryDescription
Action FailureIndicates that the defined action for the step did not execute correctly.   
Action Is Not SupportedIndicates that the specified action in the step is not defined in Qualitia or the specified action cannot be used in the selected browser or environment. 
Cannot Select From DropdownIndicates that the step did not execute as the specified drop-down list does not exist or it does not contain the option that is defined as a parameter.
Class File Is Missing In The ProjectIndicates that the custom action did not execute because its source file is missing. 
Failed To Store DataIndicates that the action related to storing data failed.
File Does Not ExistIndicates that either the specified file is not found in the specified location or the file extension is incorrect, or the step failed to create a file in the specified location.
Incorrect Data FormatIndicates that the parameters contain data in an invalid format, such as invalid date format, invalid file format, or invalid data encryption format.
Data Is Not SupportedIndicates that the parameter contains data that the object or the action does not support.
Invalid ExpressionIndicates that the conditional expression syntax or the expression provided as input parameter for an action, is invalid.
Invalid Input ParametersIndicates that the test data provided for the action is invalid.
Object Does Not ExistIndicates that the object is not found or disabled on the selected browser or environment.

Testdata Provided Empty Or NULL

Indicates that the test data is not provided for the action.
Timeout EncounteredIndicates that the associated object is not found within the specified Wait Time.

Uniqueness Violation

Indicates that the unique values are not provided for this category. For example, if a value is already used in Qualitia and you try to use the same value in custom action it is reported as a uniqueness violation.

TestCase_Cannot_Execute

Indicates that the whole test case was aborted due to reasons such as incorrect application URL, incorrect environment selected, or invalid Javascript expression.

Expected Result Not MetIndicates the result of a step is a defect when actual results and expected results are different.
Lack Of PermissionsIndicates that you do not have access to the environment or on application under test feature you are testing.

You can add custom failure categories to custom actions as per your requirement, refer to Adding a Failure Category for a Custom Action.

  1. From the Suite of Suites screen, click a test suite execution for which you want to view the failure summary.
  2. In the Test Suite Execution Summary Report, click the Failure Summary button.
    A list of associated failure categories is displayed along with the number of failed steps.
  3. Do the following in the order listed:
    1. Click a failure category associated with the test suite. 
      The failure category expands to show the list of associated test case iterations where failure has occurred.
    2. Click a test case iteration.
      A list of applicable failure categories in that test case iteration is displayed.
    3. Click a failure category associated with the selected test case iteration.
      The failure category expands to show the list of associated failed steps of the selected test case iteration.
      If the step is part of a task, then the task name and task iteration are also shown.
    4. Click a failed step.
      The associated test case iteration detailed report opens and it highlights the selected step.
    5. You can view the screenshot and info log for the failed step.

Purging Data from the Server Administration Portal

Only administrators can purge the data.

Once you purge reports data, you cannot recover them.

Purge Data Tab

  • Number of Test Execution Reports

  • Total storage size of the suite execution report data

  • Total storage size of the image data

  • Total storage size of the log data

If besides the checkbox of a test suite execution, a red alert icon is displayed, it indicates the suite execution is aborted.

Column

Description

Generated On

Indicates the date on which the report was generated.

Suite Name

Indicates the name of the test suite

Project Name

Indicates the name of the associated project

Execution Type

Indicates the execution type:

  • Qualitia denotes the test suite is executed through a QAS Client.

  • Offline denotes that the test suite is executed through an offline package, either standalone or using a CI server.

Iteration No

Indicates the iteration number of the test suite execution

Total Size

Indicates the size of reports data including screenshots and logs

Report Size

Indicates the size of reports excluding screenshots and logs

Images Size

Indicates the size of associated screenshots

Logs Size

Indicates the size of associated log files

Test Cases

Indicates the number of test cases in the test suite

Test Case Status

Indicates the number of test cases that passed, failed, have defects, and are not executed.

Purging the Selected Reports

  1. Click Purge Data.

  2. Select any or all of the following checkboxes:

    1. All Report Files: To remove all the reports data of the selected reports to remove its entire folder structure. However, the execution summary of the suite execution report is stored in the database.

    2. Images Only: To remove only the screenshots captured for the selected reports.

    3. Logs Only: To remove only the log files for the selected reports.

  3. Click Purge.
    An alert message appears that shows the number of reports and the size of files that are ready for removal.

  4. Click Continue.

Filtering the Suite Execution Reports List

  1. Select a date range or click the Filter button.

  2. Select the appropriate options from the list of filters.

Logs Tab

Column

Description

Date

Indicates the date and time when the reports were purged.

Activity

Indicates the purging activity

User

Indicates the user who purged the reports

Purge Details

Indicates the type of reports data that was removed.

Data Size

Indicates the amount of data purged

Details

Click to view the details of test suite execution reports that were purged.

Uploading Multiple Suite Execution Reports to Real Time Reporting Portal

  • From any computer
    You can directly upload the reports from your computer if its connection with Qualitia Server is steady. Also, it must have all the test suite execution reports that you want to upload.

  • From the Qualitia Server
    You can use Qualitia Server to expedite the uploading of reports as there is no chance of network connection failure.

  1. None of the reports you want to upload are:

    • Already uploaded to the Real Time Reporting portal, except for the ones that were aborted due to loss in network connectivity.

    • Incomplete as the suite execution is still in progress.

    • Generated using Qualitia version lower than 8.0.

  2. Your system must have an offline package. If your system has Qualitia client, you can create an offline package. For detailed instructions, refer to Creating an Offline Package.
    Else, you can transfer an offline package from any other computer that contains the offline package to your system.

  3. Qualitia server has enough space available. If the Real Time Reporting portal shows an error message that the available drive space is less than 10%, contact the Qualitia Admin to purge old reports to free up space.

  1. Create a folder on the system from where you want to upload the reports.

  2. Copy each suite execution report folder (ITR_xxx) that you want to upload.

  3. Open the Command Prompt, and navigate to the folder where the Qualitia offline jar is present.

  4. Enter the following code:
    java -jar qualitiaoffline-8.3.0.jar UploadReport=true QualitiaServerURL="<Qualitia_Server_URL>” ReportPath="<Report_Path>" allowScreenshots="Yes"
    The following parameters denote:

    1. QualitiaServerURL is the URL of the Qualitia Server.

    2. Report Path is the location of the folder that contains the suite execution reports

    3. allowScreenshots is used to upload the screenshots of the reports. Enter “Yes” to upload screenshots or enter “No” if you do not want to upload associated screenshots.
      Note:

      1. If you are uploading reports from Qualitia server, then you do not need to specify allowScreenshots=”Yes”.

      2. If you do not enter the allowScreenshots parameter, then by default the screenshots of the reports are uploaded.

  5. Press Enter to start uploading the reports.
    For every report, the following details are displayed:

    1. The upload progress in percentage.

    2. The confirmation message for the reports uploaded successfully and they are removed from the reports folder.

    3. The failure message for the reports that failed to upload.

  • No labels