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 Web Automation

Performing Web Automation

PreviousGuide to Web AutomationNextStandard Actions Methods

Last updated 3 years ago

Was this helpful?

To Perform Web Automation, follow the Below steps:

STEP 1: Create a and add a name according to your requirement. STEP 2: Create a and add a name according to your requirement. The Excel Files should be saved in the specific Location. For Example:

Document --> Test Data --> Product --> Code Branch --> Client --> Excel File

Note: If not saved at the specific location then the Excel File link will not be visible in the Functionality. STEP 3: Now Create a based upon the requirement.

STEP 4: Create an .

  • Naming should be similar to the web element and in Lowercase. Finding of locators.

STEP 5: Creation of .

  • Note: Product Element name should be unique.

STEP 6: Creating in the excel sheet. STEP 7: Sync the newly added test cases by clicking on sync button in test cases module.

  • Blue: Will erase all the Test data.

Red: Will newly added data in the excel sheet.

STEP 8: Once Test cases synced, create the . STEP 9: Run the Test Suite or can also make a new test run and add the functionality and test suite later. STEP 10: Finally, the desired result will be reflecting on the screen.

sync
Test Suite
Feature
Functionality
New Group
UI Element
Product Element
Test Cases