QATTS Technical Docs
2.0.0 Main
2.0.0 Main
  • QATTS Product Documentation
  • Getting Started
    • About QATTS
      • A Quick Tour of QATTS
      • Terminology
      • Relationship
    • 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
      • Database Config
      • Email Config
    • Node
      • Streaming Configuration
      • How to register node for streaming
      • Status And Actions
    • Agent
    • User
    • Role
  • Studio
    • UI Elements
      • text_box
        • Properties Library
        • Trouble Shoot
      • loader
        • Trouble Shoot
      • date
      • button
      • drop_down
        • Trouble Shoot
        • Properties Library
      • label
      • check_box
      • radio_button
      • link
      • Shadow
      • Trouble Shoot
      • Properties Library
      • Pre and Post Actions
      • table
        • Example
        • Trouble Shoot
      • form
      • toogle_button
      • file
      • alert
  • Automation
    • Objects
      • UI Element
        • Drop Down
        • Radio Button
        • Multi Elements
        • table
        • form
      • Product Element
        • Advanced Data Types
          • QIntegerArray
          • QStringArray
          • QArray
          • QData
        • Basic Data Types
      • API
      • Query
      • Smarty
        • Excel: Read data from excel
        • File: Reads file Data
        • EmailRead
        • EmailSend
        • SiteScan
        • PDF Utils
      • New Group
    • Test Case
    • Function
    • Data Table
  • 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
  • Others
    • Milestone
  • Settings
    • Builds
    • Milestone
  • Site Scan
  • Using QATTS
    • Guide to API Automation
      • Adding API
      • Request
      • Response
        • Writing Response Schema
    • Guide to Web Automation
      • Performing Web Automation
    • Guide to setup agent-service
  • Advanced Data Types
    • QData
  • Methods
  • Standard Actions Methods
    • Execute Methods
  • UI Action Methods
    • extractGroup
  • File Action Methods
  • UI Element Advanced
  • UI Checks
  • Extraction Rules
  • Assertion Operations
  • Error Codes : Automation
  • Error Code: Execution
  • JSpreadSheetUtil Methods
  • Functions
    • Primitive
      • CONCATENATE
    • Date & Time
    • Text
  • Other Information
    • FAQ
    • Troubleshooting
      • UI Methods
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

Understanding the UI element - a key component in automated web testing

PreviousObjectsNextDrop Down

Last updated 2 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

Special Locator Options

DataSetName of custom data options based locators

Locators with Test Data

Locators with Product Element Label name

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