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. Studio
  2. UI Elements
  3. table

Example

This page gives us how extraction of table data works and how to customize

First Name
Last Name
Email

Ashile

M.Smith

smith.ash@yahoo.com

Robert

H.Chan

robert.h@outlook.com

Mark

F.Flores

flores.mark@gmail.com

Leonardo

Carvalho

l.carvalho@yahoo.in

Now, let's consider the above table for extraction.

In the UI element the locator configured should give us the number of rows

Approach 1 (When we want to decide what needs to be extracted)

Under the properties section. Below Configure the below

prop.column:Your_ProductElement = Your_UIElement / LocatorType:LocatorValue

Ex : prop.column:FirstName = la.firstName

In the above format we can configure all the columns or the column's we require.

Approach 2 (When we want all the columns with auto key names)

If you have written a locator which gives all columns . Configure as below.

prop.columns.locator = Your_UIElement / LocatorType:LocatorValue

The result for the above prop will look like below

Item1 : value

Item2 : value

Item3 : value

With any approach once all the rows has been extracted. It will check for the below prop

prop.nextPage.link : UI Element / Locator Type : Locator Path

If it was configured it will navigate to each active page in the pagination and extracts the data

PrevioustableNextTrouble Shoot

Last updated 2 years ago

Was this helpful?