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

Was this helpful?

  1. Automation
  2. Objects
  3. UI Element

table

Table is ready to use component for extracting data an UI table

Table in web application is very important and complex structure holding lot of data. To simplify extracting data from a complex table, qatts have inbuilt component. Just need to config locators of the table, headers, columns and rest of it is magic created by our engineers.

Based on your scenario you can configure properties for quick results:

  • Extract selected Columns only and Map to Product Element

Use prop.column:[Product Element Name] property to define each column and respective product element

  • Extract columns without product element definition

>>Extract selected Columns and Map to Product Element

Locator Type & Path must be given for row array. Not to the table. Column locator has to be relative to row.

Use below advanced props for table element type

Prop name
Description
Options

prop.column:[Product Element Name]

Locator for respective Product Element or UI Element. For the product element name in the prop value, give locator info. Locator Info contains locator type and locator path with colon as delimiter

prop.column:First Name ( First Name is product element)

prop.column:ZipCode (ZipCode is Product Element)

Locator Info Syntax

[locator type]:[locator path]

prop.columns.locator

Generic locator to each cell. Use columnIndex variable in locator to make it dynamic

if this property is given, it will ignore individual prop.column:[Product Element Name]

prop.column.key

Typical table data will be hold data of an entity. For example a table will hold list of employee. And each row will hold information of an employee. So for employee key field that represent unique employee such as emp id or name etc. Key field for the data set that table data is representing. This is optional and but will be useful in getting the Data from array and display

A valid product element

prop.table.noDataElement

Locator to check if table don't have any data. if the element exits, its assume that data doesn't exists in the table

prop.nextPage.link

Locator info of the web element that navigates to the next page.

Optional Field. Locator to be specified as [locator type]:[locator path]

PreviousMulti ElementsNextform

Last updated 2 years ago

Was this helpful?