QATTS Technical Docs
V 3.0
V 3.0
  • QATTS Product Documentation
  • 1.Getting Started
    • About QATTS
      • A Quick Tour of QATTS
    • QATTS Terminology
    • Dashboard
  • QATTS Terminology
  • Administration
    • Product
      • How to Add Product
    • Code Branch
      • How to Add Code Branch
    • Feature
    • Clients
      • How to Add Clients
    • Deployment
      • How to Add Deployment
    • Node
  • Automation
    • Objects
      • UI Element
      • Product Element
      • API
      • Query
      • Smarty
      • New Group
    • Functionality
    • Test Data Repository
  • Execution
    • Test Case
      • Counts by Clients
      • Search and Manage
      • Context Parameters
      • Details by Functionality
      • Info and Execution
    • Test Suite
      • Create Suite
    • Test Run
      • Test Run
        • Partial Execute
      • Schedule Test Run
      • Untitled
    • Test Result
      • Results by Clients
      • Results by Fuctionality
    • Build No
    • Reports
      • All Failed Test Cases
      • Recently Failed Test Cases
  • Others
    • Milestone
    • Role
    • User
  • Settings
    • Features
    • Builds
    • Milestone
  • 2. QATTS Configuration
    • 2.1 Adding Product
    • 2.2 Create Code Branch
    • 2.3 Create Client
    • 2.4 Adding Tools
      • 2.4.1 Drop Box Integration
      • 2.4.2 Share point Integration
      • 2.4.3 Jira Integration
    • 2.5 Create Deployment
    • 2.6 Configure Execution Nodes
    • 2.7 Configure Tools
    • 2.8 Create Roles
    • 2.9 Create Users
    • 2.9 Manage Configuration
      • 2.10.1 Manage Product
      • 2.10.2 Manage Code Branch
      • 2.10.3 Manage Client
      • 2.10.4 Manage Deployment
      • 2.10.5 Manage Requirements
      • 2.10.6 Manage Workflows
      • 2.10.7 Manage User
      • 2.10.9 Manage Tools
  • 3. Test Script development
    • 3.1 Manual Test Script development
      • 3.1.1 Create Manual Functionality
      • 3.1.2 Adding Test Case
      • 3.1.3 Adding Test Data
    • 3.2 Automated Test Script Development
      • 3.2.1 Adding Object Groups
        • 3.2.1.1 Create UI Elements
        • 3.2.1.2 Create Product Element
        • 3.2.1.3 Create API Objects
          • 3.2.1.3.1 API Parameterization
          • 3.2.1.3.2 Data Extraction
          • 3.2.1.3.3 Data Assertion
        • 3.2.1.4 Create Query
        • 3.2.1.5 Create Smarty
      • 3.2.2 Adding Functionalities
        • 3.2.2.1 Create Functionality
        • 3.2.2.2 Adding Test Script (Action Class)
  • 4. Test Execution
    • 4.1 Manual Test Execution
      • 4.1.1 Creating Test runs
      • 4.1.2 Assign for Test Run
    • 4.2 Automated Test Execution
      • 4.2.1 Creating Test Runs
      • 4.2.2 Scheduling Test Runs
  • 5. Manage Features
    • 5.1 Create Feature
    • 5.2 Create Build
    • 5.3 Create Milestone
  • 6. How to - Guides
    • 6.1 How to Automate Web Application
    • 6.2 How to Automate Mobile Application
    • 6.3 How to Automate API
    • 6.4 How to Automate Desktop Applications
  • Standard Actions Methods
  • UI Action Methods
  • Error Codes : Automation
  • Error Code: Execution
  • Smarties
    • File: Reads file Data
  • API Automation
    • Guide to API Automation
      • Base Terms of API
      • Request
      • Response
        • Writing Response Schema
  • Web Automation
    • Guide to Web Automation
  • Others
    • FAQ
Powered by GitBook
On this page

Was this helpful?

  1. 1.Getting Started

QATTS Terminology

Product : Product defines the scope of application to be automated like Web, Desktop, Mobile, API, etc. The test data repository is maintained in product.

Code Branch : Code branch is a repository where we are maintaining all the test data, workflows, elements, etc. Code branch is nothing but maintaining the version of an application.Example: staging environment, production environment

Client : If a product has multiple clients, we need to maintain the test data and task executions for each clientt. If product doesn't have clients, we can maintain the test data and task executions at code branch level itself and no need to create client.

Deployment : Deployment holds all the environment details like URL and data base details.

UI Element : UI element is an object of DOM. Every element/field of the webpage like textbox, button, checkbox, etc... will have associated identifiers. We need to collect the unique identifiers for every page for automation needs.

Product Element : Any HTML Element which has the associated test data is a product element.

Query : Query is retrieving data from the database by using the data base queries.

Smarty : Smarty is nothing but extracting the data from CAPTCHA element and reading data from the email and sending data to the email.

PreviousA Quick Tour of QATTSNextDashboard

Last updated 3 years ago

Was this helpful?