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. Using QATTS
  2. Guide to API Automation

Adding API

PreviousGuide to API AutomationNextRequest

Last updated 3 years ago

Was this helpful?

In this Chapter you will be given a overview of API Testing with QATTS.

The following is the description of adding an API in detail:

  • API Name: Giving proper name for the API based on the module.

  • Description: Giving proper description related to module that you are going to work on.

  • Type: Giving the Type of response.

    • REST (Representational State Transfer) - This is used when the request and response format are not in XML, i.e. it can be in JSON, HTML or any other format.

    • SOAP( Simple Object Access Protocol) - This is used when the request and response format of the API are in the XML format.

  • Select Group: Select the Group name.

  • HTTP Methods: Select the HTTP Method that needs to be performed on the API.

    • Note: POST, PUT, PATCH will have the request template( Need an Input to test API). GET will not have the request template unless for some special conditions.

  • Here by clicking on the Eye you can select the deployment that you are going work on.

Then Click on the Save Button.

Once saved more options are now visible to work with.