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. API Automation
  2. Guide to API Automation
  3. Response

Writing Response Schema

PreviousResponseNextGuide to Web Automation

Last updated 3 years ago

Was this helpful?

The Following is the process to Write a Response Schema First Click on the 3 dotted icon and click on the NEW.

After that give Name and Match String as per the requirement.

  • Name - Here we give the name that is related to response body.

  • Match String - Here we give the any Key parameter of the response body which should be as it is in the response body.

Click on the three dots and Select the Name value that you have given and save the data.

In the lower sections it contains Response Field value, DataType , Assert Operation, Assert Data and Product Element(optional).

Response Field Value - This is to map the Key parameter in the Response Body, in other words here we are locating the element in the response body so that we can check that if it is equal to the input element that we have given in the request template.

Data Type - This depends on the value parameter i.e if it is an numerical value we use Integer, if it is Alphabets we use String as data type, if it is true or false then we use Boolean as Data Type.

Assertion Operation- Here we give the operator based on the requirement such =, >=,<,> for the Integer data type, and for string data type we use equals, Stringlength= e.t.c.

Assert Data- There are two ways to Assert the data.

  • By Parameterized Product Element - Here we give ${Productelement} in this format which was parameterized in the request which helps to check the data from the response is equal to the request that had given from the default param.

  • By Giving Raw Data - Here the expected data will be given. for example if we take statusCode in API Header we expect the outcome as 200, so we can type 200 as the outcome.

Product Element - This is for filtering the data in the output that needed. For example, in the response it has 40 lines of data but if checked only 2-3 lines of data shown, by giving product element of selected data it can acquire required data output.