QATTS Technical Docs
1.0.0 Prev
1.0.0 Prev
  • QATTS Product Documentation
  • Getting Started
    • About QATTS
    • Dashboard
  • Getting to know
  • Administration
    • Product
      • How to Add Product
      • Configure Test Data Repository
    • Code Branch
      • How to Add Code Branch
    • Feature
    • Client
      • How to Add Client
    • Deployment
      • How to Add Deployment
    • Node
    • User
    • Role
  • Automation
    • Objects
      • UI Element
      • Product Element
        • Advanced Data Types
          • QIntegerArray
          • QStringArray
          • QData
        • Basic Data Types
      • API
      • Query
      • Smarty
      • New Group
    • Functionality
    • Test Data Repository
  • Execution
    • Test Case
      • Clients Summary
      • Search and Manage
      • Context Parameters
      • Details by Functionality
        • Sync
    • Test Suite
      • Create Suite
    • Test Run
      • Schedule Test Run
      • Untitled
    • Test Result
      • Results by Clients
      • Results by Fuctionality
    • Build No
    • Reports
      • All Failed Test Cases
      • Recently Failed Test Cases
  • Settings
    • Build
    • Milestone
  • Smarties
    • Excel: Read data from excel
    • File: Reads file Data
  • Using QATTS
    • Guide to API Automation
      • Adding API
      • Request
      • Response
        • Writing Response Schema
    • Guide to Web Automation
      • Performing Web Automation
  • Methods
  • Standard Actions Methods
    • setRunValue
    • performAPIFieldLevel
    • Execute Function
    • Execute WorkFlow
    • Execute Test Case
    • Send Request
    • Assert Data
    • Get Run Value
  • UI Element Advanced
    • table
  • UI Action Methods
    • Assertion Methods
      • Assert Groups
      • Assert Product Element
      • Assert HTML Element
      • StateCheck
    • extractGroup
    • Data Population Methods
      • Populate Group
      • Populate Alert
      • Populate Field
    • Link Methods
      • Check Broken Links
      • Extract Link
    • Other UI Action Methods
      • Perform Field Level QAction
      • Perform Element Checks
      • Perfrom Page Checks
      • Wait for Invisibility of Element
      • Get Table Data
      • Refresh Page
      • Alert Action
      • Get Element Size
      • Perform Named Action
  • Error Codes : Automation
  • Error Code: Execution
  • Other Information
    • FAQ
    • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Getting Started

Dashboard

PreviousAbout QATTSNextAdministration

Last updated 3 years ago

Was this helpful?

The Dashboard in QATTS makes it easy for an user to understand the current status of the testcases. The filters on the dashboard further allow the viewer to narrow the dashboard's results to only the data the viewer is interested in.

QATTS dashboard has two main filters on the top left corner viz Product & Code Branch

Product: Clicking on the will enable user to switch from one product to other. To make the selected product as default selection click on the radio button of the desired product. This default product will become the users favorite Product on his/her subsequent logins.

Code Branch: You can select or deselect a from the available options. The Code Branch varies depending on the selection of the Product. The data results on the dashboard will be shown for the selected Code Branch.

Similar to Product, the user can make a particular Code Branch as his default Code Branch by selecting the radio button.

Deployment: Select the as per your target application Environment. The dashboard's data for the selection varies depending on the Code Branch, the Product and the Deployment the user has selected.

Client: Select a on which you would be performing the testing. The visible selections of clients are based upon the product user has selected. Again, the dashboard results will further narrowed down with the selected Client.

The QATTS dashboard has three cards/layouts to give users a clear view of the information that matters most. The most critical content is simplified with visual elements using charts.

All Test Cases Status: The status of the test cases is represented in a Doughnut chart: how many test cases are passed, how many failed and yet to run.

The Analyze link at bottom redirects the view to the Test Result by clients, where QATTS gives you a detailed view of all the test cases.

Functionality Test Cases Status: Here test cases are segregated according to the functionality names. It shows how many test cases to be run, failed or yet to run.

Latest 5 Test Runs: It displays the recent five test cases executed in the application for the selected Product and Code Branch

Product
Code Branch
Deployment
Client