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. drop_down

Properties Library

Answers to yours questions / Exceptions

Property Name
Property Value
When to use
How it works

byValue

TRUE / FALSE

  1. When the user required value is saved in the attribute "value"

  2. When the value was saved in the hidden attribute

It finds the web element matching the with the attribute value == given test data Note : Works only for select tags

byIndex

TRUE / FALSE

  1. When the user required value is in maintained in a fixed index all the time

It finds the web element matching with the given index number in the tets data Note : Works only for select tags

byname

TRUE / FALSE

When the user required value is saved in the attribute "name"

It finds the web element matching the with the attribute value == given test data Note : Works only for select tags

tagName

YOUR TAG NAME

It is a special property when the dropdown is not authentic. Here user has to provied the tagName value. Ex : dropdown has values in "li" tags. Then we have to configure as tagName : li

QATTS frames the XPATH locator internally with the test data given. Finds and clicks the element.

  1. Contains

  2. tagName

  1. TRUE / FALSE

  2. YOUR TAG NAME

This works same as above. The only difference is. When we have the partial text provided in the test data. This will work

QATTS frames the XPATH locator internally with the test data given. Finds and clicks the element.

custom

YOUR_XPATH

When we have to write a complex XPATH and then replace a value inside it using parameterization ${} in the given locator

QATTS evaluates the given XPATH. Finds and clicks the element.

Note : When configuring the tagName, contains, Custom -> Main locator should be configured to match the main click and tagName should match the value.

PreviousTrouble ShootNextlabel

Last updated 2 years ago

Was this helpful?