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
  • What is UI Element?
  • Create a UI Element
  • Step by step walkthrough
  • Short video

Was this helpful?

  1. Automation
  2. Objects

UI Element

PreviousObjectsNextProduct Element

Last updated 3 years ago

Was this helpful?

What is UI Element?

UI elements are integral part of a web application. They are responsible for interactions between the user and the application.

Refer

UI elements can be uniquely identified by their locators.

A locator is a command that tells QATTS to locate a particular UI element.

Create a UI Element

Step by step walkthrough

To add an UI Element follow the below steps

STEP 1: Log into QATTS goto Studio on the left navigation panel, it directs to new window which will be appearing as shown below.

STEP 2: On the right corner Click on "+" icon and select Add UI Element, it should appear as below.

STEP 3: Fill the required details as shown in the below screenshot.

while filling Wait Type select " Time" and in Wait Value add value of at least "3 seconds".

  • UI Element Name: The name could any of the user choice.

  • UI Element Type: The user need to choose the type of the element such as button, text, file etc.

  • HTML Linking: User need to define type of linking as xpath or others.

  • Locator path: Here the locator id need to added.

  • Wait Type: Here time is the default selection.

  • Wait Time: Here user can add how many seconds the application searches for the locator.

STEP 4: After adding required details and then click on Save, the given UI Element name would be saved in the groups you have selected it in.

Short video

https://www.uxpin.com/studio/blog/user-interface-elements-every-designer-should-know/