testcentricity_web 4.1.10 → 4.2.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 23887c7085c3a17d09449043491877a3cce346498b778d3e44c3e9aeacad0bdf
-  data.tar.gz: 6425f62243f5795ac091814a1a68e6b08d44d219862bc6c26fc5244afb16a456
+  metadata.gz: 6bba95ce17cd2e367f22261389fbe57cf7599ad7c8b376d293713929363dc7b2
+  data.tar.gz: e0e50d77d9e41d22652d6345820ef4258c31ff8e0ec63171fcfd6bba4bf8da17
 SHA512:
-  metadata.gz: db06316bf646dac6ea37407286059429141d25433c39863cde90b915d7714cb281e28fe116fc997faefff1c98711835ad88f9be0fbea35a66b5e756b14da8236
-  data.tar.gz: d11596401fb3288e73a1cab6b3bbf6f5443f4e1cc6c94ed2be43c38096e48335126c70aa3851530df190f7ac6b1b1c576bd2a71fd51a123e5ccaf51c6e7b1772
+  metadata.gz: ab4055f869598ce042c6b62172b8a89e9632268593dfcfec4cf4c7b401cfd66c3dfbfdd177f046aa429f80f575dd88558be187447cfcecd7ab2a32fa355cff78
+  data.tar.gz: 3c0581ac5599a71203eeb592f919de7a539ebb0855a2e3dd72cf9de2ae9a4ca69ecb7bf7b408a1540a432c1358337803ddc84eaf8d1827d6033904aa35f9e542

data/CHANGELOG.md

@@ -2,6 +2,81 @@
 All notable changes to this project will be documented in this file.
 
 
+## [4.2.6] - 12-JUNE-2022
+
+### Fixed
+* Fix `gemspec` to no longer include specs and cuke tests as part of deployment package for gem.
+
+
+## [4.2.5] - 10-JUNE-2022
+
+### Fixed
+*`WebDriverConnect.initialize_web_driver` method no longer raises `No such file or directory @ dir_s_mkdir` error due to
+missing `Downloads` folder when running tests in parallel.
+
+
+## [4.2.4] - 02-JUNE-2022
+
+### Added
+* Added `UIElement.wait_until_enabled` method
+
+
+## [4.2.3] - 01-JUNE-2022
+
+### Added
+* Added `UIElement.wait_while_busy` method
+* Updated `PageObject.verify_ui_states` and `PageSection.verify_ui_states` methods to support verification of `aria_busy` attribute.
+
+
+## [4.2.2] - 21-MAY-2022
+
+### Changed
+* Update default version of Appium used when running tests on Sauce Labs service.
+* Refactored capabilities definition when running with locally hosted Appium instance.
+
+
+## [4.2.1] - 23-APR-2022
+
+### Added
+* Added the following `Audio`, `Media`, and `Video` methods to support verification of media text tracks (subtitles, captions,
+chapters, descriptions, or metadata):
+  * `track_count`
+  * `active_track`
+  * `active_track_data`
+  * `all_tracks_data`
+  * `track_data`
+  * `active_track_source`
+  * `track_source`
+* Updated `PageObject.verify_ui_states` and `PageSection.verify_ui_states` methods to support verification of the following
+  `Media` properties:
+  * `:track_count`
+  * `:active_track`
+  * `:active_track_data`
+  * `:all_tracks_data`
+  * `:track_data`
+  * `:active_track_source`
+  * `:track_source`
+
+
+## [4.2.0] - 20-APR-2022
+
+### Added
+* `TextField.validation_message` and `TextField.validity?` methods added.
+* Updated `PageObject.verify_ui_states` and `PageSection.verify_ui_states` methods to support verification of the following
+`TextField.validity?` properties:
+  * `:badInput`
+  * `:customError`
+  * `:patternMismatch`
+  * `:rangeOverflow`
+  * `:rangeUnderflow`
+  * `:stepMismatch`
+  * `:tooLong`
+  * `:tooShort`
+  * `:typeMismatch`
+  * `:valid`
+  * `:valueMissing`
+
+
 ## [4.1.10] - 19-APR-2022
 
 ### Fixed
@@ -19,7 +94,6 @@ running gem test specs and features.
 radio buttons to the unchecked state.
 
 ### Added
-
 * `CheckBox.define_custom_elements` and `Radio.define_custom_elements` methods now support specifying a child `input` component
 contained by a top level `label` element.
 

data/README.md

@@ -1,18 +1,19 @@
 # TestCentricity™ Web
 
 [![Gem Version](https://badge.fury.io/rb/testcentricity_web.svg)](https://badge.fury.io/rb/testcentricity_web)  [![License (3-Clause BSD)](https://img.shields.io/badge/license-BSD%203--Clause-blue.svg?style=flat-square)](http://opensource.org/licenses/BSD-3-Clause)
+![Gem Downloads](https://img.shields.io/gem/dt/testcentricity_web) ![Maintained](https://img.shields.io/maintenance/yes/2022)
 
 
-The TestCentricity™ Web core generic framework for desktop and mobile web browser-based app testing implements a Page Object Model DSL
-for use with Cucumber, Capybara (version 3.x), and Selenium-Webdriver (version 4.x). It also facilitates the configuration of the appropriate
+The TestCentricity™ Web core framework for desktop and mobile web browser-based app testing implements a Page Object Model DSL for use
+with Cucumber (version 7.x or greater), Capybara (version 3.x), and Selenium-Webdriver (version 4.x). It also facilitates the configuration of the appropriate
 Selenium-Webdriver capabilities required to establish a connection with a local or cloud hosted desktop or mobile web browser.
 
 The TestCentricity™ Web gem supports running automated tests against the following web test targets:
 * locally hosted desktop browsers (Chrome, Edge, Firefox, Safari, or IE)
 * locally hosted "headless" Chrome, Firefox, or Edge browsers
 * remote desktop and emulated mobile web browsers hosted on Selenium Grid 4 and Dockerized Selenium Grid 4 environments
-* mobile Safari browsers on iOS device simulators or physical iOS devices (using Appium and XCode on OS X)
-* mobile Chrome or Android browsers on Android Studio virtual device emulators (using Appium and Android Studio on OS X)
+* mobile Safari browsers on iOS device simulators or physical iOS devices (using Appium and XCode on macOS)
+* mobile Chrome or Android browsers on Android Studio virtual device emulators (using Appium and Android Studio on macOS)
 * cloud hosted desktop (Firefox, Chrome, Safari, IE, or Edge) or mobile (iOS Mobile Safari or Android) web browsers using the following service:
   * [Browserstack](https://www.browserstack.com/list-of-browsers-and-platforms?product=automate)
   * [Sauce Labs](https://saucelabs.com/open-source#automated-testing-platform)
@@ -29,13 +30,14 @@ A complete history of bug fixes and new features can be found in the {file:CHANG
 
 The RubyDocs for this gem can be found [here](https://www.rubydoc.info/gems/testcentricity_web).
 
-An example project that demonstrates the implementation of a page object model framework using Cucumber and TestCentricity™
+An example project that demonstrates the implementation of a page object model framework using Cucumber and TestCentricity™ Web
 can be found [here](https://github.com/TestCentricity/tc_web_sample).
 
 
 ## Installation
 
-TestCentricity version 4.1 and above requires Ruby 2.7 or later. To install the TestCentricity gem, add this line to your automation project's Gemfile:
+TestCentricity Web version 4.1 and above requires Ruby 2.7.5 or later. To install the TestCentricity Web gem, add this line to your
+automation project's Gemfile:
 
     gem 'testcentricity_web'
 
@@ -59,7 +61,7 @@ If you are using Cucumber, you need to require the following in your `env.rb` fi
 
 ### Using RSpec
 
-If you are using RSpec instead, you need to require the following in your `env.rb` file:
+If you are using RSpec instead, you need to require the following in your `spec_helper.rb` file:
 
     require 'capybara'
     require 'capybara/rspec'
@@ -69,7 +71,7 @@ If you are using RSpec instead, you need to require the following in your `env.r
 ### Using Appium
 
 If you will be running your tests on mobile Safari browsers on simulated iOS devices using Appium and XCode Simulators, you need to require
-the following in your `env.rb` file:
+the following in your `env.rb` and/or `spec_helper.rb` file:
 
     require 'appium_capybara'
 
@@ -118,22 +120,22 @@ Web pages typically have names and URLs associated with them. Web pages also typ
 indicates that the page's contents have fully loaded.
 
 The `page_name` trait is registered with the `PageManager` object, which includes a `find_page` method that takes a page name as a
-parameter and returns an instance of the associated `Page Object`. If you intend to use the `PageManager`, you must define a `page_name`
+parameter and returns an instance of the associated `PageObject`. If you intend to use the `PageManager`, you must define a `page_name`
 trait for each `PageObject` to be registered.
 
 The `page_name` trait is usually a `String` value that represents the name of the page that will be matched by the `PageManager.findpage` method.
 `page_name` traits are case and white-space sensitive. For pages that may be referenced with multiple names, the `page_name` trait may also be
 an `Array` of `String` values representing those page names.
 
+A `page_locator` trait is defined if a page has a unique object or attribute that exists once the page's contents have fully loaded. The
+`page_locator` trait is a CSS or Xpath expression that uniquely identifies the object or attribute. The `verify_page_exists` method waits
+for the `page_locator` trait to exist.
+
 A `page_url` trait should be defined if a page can be directly loaded using a URL. If you set Capybara's `app_host`, or specify a base URL
 when calling the `WebDriverConnect.initialize_web_driver` method, then your `page_url` trait can be the relative URL slug that will
 be appended to the base URL specified in `app_host`. Specifying a `page_url` trait is optional, as not all web pages can be directly loaded
 via a URL.
 
-A `page_locator` trait is defined if a page has a unique object or attribute that exists once the page's contents have fully loaded. The
-`page_locator` trait is a CSS or Xpath expression that uniquely identifies the object or attribute. The `verify_page_exists` method waits
-for the `page_locator` trait to exist.
-
 You define your page's **Traits** as shown below:
 
     class LoginPage < TestCentricity::PageObject
@@ -387,8 +389,7 @@ You add a `PageSection` to its associated `PageObject` as shown below:
 Once your `PageObject` has been instantiated, you can call its `PageSection` methods as shown below:
 
     home_page.search_form.search_for('ocarina')
-    
-    
+
 
 ## UIElements
 
@@ -402,9 +403,9 @@ all UI elements are based on the `UIElement` class.
 
 Single `UIElement` declarations have the following format:
                                      
-    elementType :element Name, locator
+    elementType :elementName, locator
 
-* The `element name` is the unique name that you will use to refer to the UI element and is specified as a `Symbol`.
+* The `elementName` is the unique name that you will use to refer to the UI element and is specified as a `Symbol`.
 * The `locator` is the CSS or XPath attribute that uniquely and unambiguously identifies the `UIElement`.
 
 Multiple `UIElement` declarations for a collection of elements of the same type can be performed by passing a hash table containing the
@@ -475,8 +476,8 @@ Supported `UIElement` elementTypes and their declarations have the following for
 
 
 Refer to the Class List documentation for the `PageObject` and `PageSection` classes for details on the class methods used for declaring
-and instantiating `UIElements`. Examples of UI element declarations can be found in the ***Adding UI Elements to your Page Object*** and
-***Adding UI Elements to your PageSection Object*** sections above.
+and instantiating `UIElements`. Examples of UI element declarations can be found in the ***Adding UI Elements to your PageObject*** and
+***Adding UI Elements to your PageSection*** sections above.
 
 
 ### UIElement Inherited Methods
@@ -526,8 +527,10 @@ With TestCentricity, all UI elements are based on the `UIElement` class, and inh
     element.wait_until_gone(seconds)
     element.wait_until_visible(seconds)
     element.wait_until_hidden(seconds)
+    element.wait_until_enabled(seconds)
     element.wait_until_value_is(value, seconds)
     element.wait_until_value_changes(seconds)
+    element.wait_while_busy(seconds)
 
 **WAI-ARIA Object Accessibility (A11y) methods:**
 
@@ -581,7 +584,7 @@ of a hex color `String`. For `section` objects, data values must be a `String`,
 The `populate_data_fields` method verifies that data attributes associated with each `UIElement` is not `nil` or `empty` before attempting to
 enter data into the `UIElement`.
 
-The optional `wait_time` parameter is used to specify the time (in seconds) to wait for each `UIElement` to become become viable for data entry
+The optional `wait_time` parameter is used to specify the time (in seconds) to wait for each `UIElement` to become viable for data entry
 (the `UIElement` must be visible and enabled) before entering the associated data value. This option is useful in situations where entering data,
 or setting the state of a `UIElement` might cause other `UIElements` to become visible or active. Specifying a wait_time value ensures that the
 subsequent `UIElements` will be ready to be interacted with as states are changed. If the wait time is `nil`, then the wait time will be 5 seconds.
@@ -659,6 +662,21 @@ The `verify_ui_states` method supports the following property/state pairs:
     :max         Integer
     :step        Integer
 
+  Text Field Constraint validation
+
+    :validation_message String
+    :badInput           Boolean
+    :customError        Boolean
+    :patternMismatch    Boolean
+    :rangeOverflow      Boolean
+    :rangeUnderflow     Boolean
+    :stepMismatch       Boolean
+    :tooLong            Boolean
+    :tooShort           Boolean
+    :typeMismatch       Boolean
+    :valid              Boolean
+    :valueMissing       Boolean
+
 **Checkboxes:**
 
     :checked       Boolean
@@ -722,6 +740,13 @@ The `verify_ui_states` method supports the following property/state pairs:
     :volume                Float
     :preload               String
     :poster                String
+    :track_count           Integer
+    :active_track          Integer
+    :active_track_data     Hash
+    :all_tracks_data       Array of Hash
+    :track_data            Hash
+    :active_track_source   String
+    :track_source          String
 
 #### ARIA accessibility property/state pairs
 
@@ -740,6 +765,7 @@ The `verify_ui_states` method supports the following ARIA accessibility property
     :aria_checked         Boolean
     :aria_readonly        Boolean
     :aria_pressed         Boolean
+    :aria_busy            Boolean
     :aria_haspopup        Boolean
     :aria_sort            String
     :aria_rowcount        String
@@ -1022,7 +1048,7 @@ cumbersome to manage if your web application has dozens of `PageObjects` that ne
 ### Using the PageManager
 
 The `PageManager` class provides methods for supporting the instantiation and management of `PageObjects`. In the code example below,
-the `page_objects` method contains a hash table of your `PageObject` instances and their associated `PageObject` class names to be 
+the `page_objects` method contains a hash table of your `PageObject` instances and their associated `PageObject` classes to be 
 instantiated by `PageManager`:
     
     module WorldPages
@@ -1161,24 +1187,24 @@ The `TestCentricity::WebDriverConnect.initialize_web_driver` method configures t
 establish a connection with a target web browser, and sets the base host URL of the web site you are running your tests against.
 
 The `TestCentricity::WebDriverConnect.initialize_web_driver` method accepts a single optional parameter - the base host URL. Cucumber
-**Environment Variables** are used to specify the target local or remote web browser, and the various webdriver capability parameters required to configure
-the connection.
+**Environment Variables** are used to specify the target local or remote web browser, and the various webdriver capability parameters required
+to configure the connection.
 
 
 ### Locally hosted desktop web browser
 
-For locally hosted desktop web browsers running on macOS (OS X) or Windows platforms, the `WEB_BROWSER` Environment Variable must be set to one of the
+For locally hosted desktop web browsers running on macOS or Windows platforms, the `WEB_BROWSER` Environment Variable must be set to one of the
 values from the table below: 
 
 | `WEB_BROWSER`      | **Desktop Platform**                           |
 |--------------------|------------------------------------------------|
-| `chrome`           | OS X or Windows                                |
-| `chrome_headless`  | OS X or Windows (headless - no visible UI)     |
-| `firefox`          | OS X or Windows |
-| `firefox_headless` | OS X or Windows (headless - no visible UI)     |
-| `edge`             | OS X or Windows                                |
-| `edge_headless`    | OS X or Windows (headless - no visible UI)     |
-| `safari`           | OS X only                                      |
+| `chrome`           | macOS or Windows                               |
+| `chrome_headless`  | macOS or Windows (headless - no visible UI)    |
+| `firefox`          | macOS or Windows                               |
+| `firefox_headless` | macOS or Windows (headless - no visible UI)    |
+| `edge`             | macOS or Windows                               |
+| `edge_headless`    | macOS or Windows (headless - no visible UI)    |
+| `safari`           | macOS only                                     |
 | `ie`               | Windows only (IE version 10.x or greater only) |
 
 Refer to **section 8.6 (Using Browser specific Profiles in cucumber.yml)** below.
@@ -1236,7 +1262,7 @@ A detailed list of file MIME types can be found [here](https://www.freeformatter
 
 ### Locally hosted emulated mobile web browser
 
-You can run your tests against mobile device browsers that are emulated within a locally hosted instance of a Chrome desktop browser on OS X or
+You can run your tests against mobile device browsers that are emulated within a locally hosted instance of a Chrome desktop browser on macOS or
 Windows. The specified mobile browser's user agent, CSS screen dimensions, and default screen orientation will be automatically set within the
 local Chrome browser instance. You may even specify the emulated device's screen orientation. For locally hosted emulated mobile web browsers,
 the `WEB_BROWSER` Environment Variable must be set to one of the values from the table below: 
@@ -1347,7 +1373,7 @@ Refer to **section 8.6 (Using Browser specific Profiles in cucumber.yml)** below
 #### Mobile Safari browser on iOS Simulators or iOS Physical Devices
 
 You can run your mobile web tests against the mobile Safari browser on simulated iOS devices or physically connected iOS devices using Appium and XCode on
-OS X. You must install Appium, XCode, and the iOS version-specific device simulators for XCode. You must also ensure that the `appium_capybara` gem is
+macOS. You must install Appium, XCode, and the iOS version-specific device simulators for XCode. You must also ensure that the `appium_capybara` gem is
 installed and required as described in **section 3.3 (Setup - Using Appium)** above.
 
 Information about Appium setup and configuration requirements for testing on physically connected iOS devices can be found on [this page](https://github.com/appium/appium/blob/master/docs/en/drivers/ios-xcuitest-real-devices.md).
@@ -1388,7 +1414,7 @@ Refer to **section 8.6 (Using Browser specific Profiles in cucumber.yml)** below
 
 #### Mobile Chrome or Android browsers on Android Studio Virtual Device emulators
 
-You can run your mobile web tests against the mobile Chrome or Android browser on emulated Android devices using Appium and Android Studio on OS X. You
+You can run your mobile web tests against the mobile Chrome or Android browser on emulated Android devices using Appium and Android Studio on macOS. You
 must install Android Studio, the desired Android version-specific virtual device emulators, and Appium. Refer to [this page](http://appium.io/docs/en/drivers/android-uiautomator2/index.html)
 for information on configuring Appium to work with the Android SDK. You must also ensure that the `appium_capybara` gem is installed and required as
 described in **section 3.3 (Setup - Using Appium)** above.
@@ -1524,6 +1550,7 @@ for information regarding the specific capabilities.
 | `NETWORK_LOGS`           | [Optional] Capture network logs (`true` or `false`)                                                                                                                        |
 | `APPIUM_LOGS`            | [Optional] Generate Appium logs (`true` or `false`)                                                                                                                        |
 
+
 #### Remote desktop browsers on the Sauce Labs service
 
 For remotely hosted desktop web browsers on the Sauce Labs service, the following **Environment Variables** must be set as described in the
@@ -1543,6 +1570,7 @@ to obtain information regarding the specific capabilities.
 | `BROWSER_SIZE `          | [Optional] Specify width, height of browser window                                                                         |
 | `RECORD_VIDEO`           | [Optional] Enable screen video recording during test execution (`true` or `false`)                                         |
 
+
 #### Remote desktop browsers on the TestingBot service
 
 For remotely hosted desktop web browsers on the TestingBot service, the following **Environment Variables** must be set as described in
@@ -1561,6 +1589,7 @@ regarding the specific capabilities.
 | `RESOLUTION`             | [Optional] Possible values: `800x600`, `1024x768`, `1280x960`, `1280x1024`, `1600x1200`, `1920x1200`, `2560x1440` |
 | `BROWSER_SIZE`           | [Optional] Specify width, height of browser window                                                                |
 
+
 #### Remote desktop browsers on the LambdaTest service
 
 For remotely hosted desktop web browsers on the LambdaTest service, the following **Environment Variables** must be set as described in the table
@@ -1582,6 +1611,7 @@ to obtain information regarding the specific capabilities.
 | `ALLOW_COOKIES`          | [Optional] Allow all cookies (`true` or `false`) - for Safari browsers only              |
 | `CONSOLE_LOGS`           | [Optional] Used to capture browser console logs.                                         |
 
+
 ### Using Browser specific Profiles in cucumber.yml
 
 While you can set **Environment Variables** in the command line when invoking Cucumber, a preferred method of specifying and managing
@@ -1722,6 +1752,8 @@ that you intend to connect with.
     
     #==============
     # profiles for remotely hosted web browsers on the BrowserStack service
+    # WARNING: Credentials should not be stored as text in your cucumber.yml file where it can be exposed by anyone with access
+    #          to your version control system
     #==============
     
     browserstack: WEB_BROWSER=browserstack BS_USERNAME="<INSERT USER NAME HERE>" BS_AUTHKEY="<INSERT PASSWORD HERE>"
@@ -1752,6 +1784,8 @@ that you intend to connect with.
     
     #==============
     # profiles for remotely hosted web browsers on the SauceLabs service
+    # WARNING: Credentials should not be stored as text in your cucumber.yml file where it can be exposed by anyone with access
+    #          to your version control system
     #==============
     
     saucelabs:  WEB_BROWSER=saucelabs SL_USERNAME="<INSERT USER NAME HERE>" SL_AUTHKEY="<INSERT PASSWORD HERE>" DATA_CENTER="<INSERT DATA CENTER HERE"
@@ -1776,6 +1810,8 @@ that you intend to connect with.
     
     #==============
     # profiles for remotely hosted web browsers on the TestingBot service
+    # WARNING: Credentials should not be stored as text in your cucumber.yml file where it can be exposed by anyone with access
+    #          to your version control system
     #==============
     
     testingbot: WEB_BROWSER=testingbot TB_USERNAME="<INSERT USER NAME HERE>" TB_AUTHKEY="<INSERT PASSWORD HERE>"
@@ -1795,6 +1831,8 @@ that you intend to connect with.
 
     #==============
     # profiles for remotely hosted web browsers on the LambdaTest service
+    # WARNING: Credentials should not be stored as text in your cucumber.yml file where it can be exposed by anyone with access
+    #          to your version control system
     #==============
     
     lambdatest: WEB_BROWSER=lambdatest LT_USERNAME=<INSERT USER NAME HERE> LT_AUTHKEY=<INSERT PASSWORD HERE>
@@ -1877,7 +1915,7 @@ area sub-folders as needed. Likewise, `PageSection` class definitions should be
 
 ## Web Test Automation Framework Implementation
 
- <img src="https://i.imgur.com/eukmEan.jpg" alt="TestCentricity Web Framework Overview" title="TestCentricity Web Framework Overview">
+ <img src="https://i.imgur.com/lCT9HbK.jpg" alt="TestCentricity Web Framework Overview" title="TestCentricity Web Framework Overview">
 
 
 

data/lib/testcentricity_web/data_objects/environment.rb

@@ -415,4 +415,3 @@ module TestCentricity
     # :nocov:
   end
 end
-

data/lib/testcentricity_web/version.rb

@@ -1,3 +1,3 @@
 module TestCentricityWeb
-  VERSION = '4.1.10'
+  VERSION = '4.2.6'
 end

data/lib/testcentricity_web/web_core/page_objects_helper.rb

@@ -9,7 +9,7 @@ module TestCentricity
     attr_accessor :locator_type
 
     XPATH_SELECTORS = ['//', '[@', '[contains(']
-    CSS_SELECTORS   = ['#', ':nth-child(', ':first-child', ':last-child', ':nth-of-type(', ':first-of-type', ':last-of-type', '^=', '$=', '*=', ':contains(']
+    CSS_SELECTORS   = %w[# :nth-child( :first-child :last-child :nth-of-type( :first-of-type :last-of-type ^= $= *= :contains(]
 
     def set_locator_type(locator = nil)
       locator = @locator if locator.nil?
@@ -139,6 +139,16 @@ module TestCentricity
                      ui_object.ready_state
                    when :volume
                      ui_object.volume
+                   when :track_count
+                     ui_object.track_count
+                   when :active_track
+                     ui_object.active_track
+                   when :active_track_data
+                     ui_object.active_track_data
+                   when :active_track_source
+                     ui_object.active_track_source
+                   when :all_tracks_data
+                     ui_object.all_tracks_data
                    when :crossorigin
                      ui_object.crossorigin
                    when :preload
@@ -181,6 +191,8 @@ module TestCentricity
                      ui_object.aria_describedby
                    when :aria_live
                      ui_object.aria_live
+                   when :aria_busy
+                     ui_object.aria_busy?
                    when :aria_selected
                      ui_object.aria_selected?
                    when :aria_hidden
@@ -231,6 +243,30 @@ module TestCentricity
                      ui_object.aria_multiselectable?
                    when :content_editable
                      ui_object.content_editable?
+                   when :validation_message
+                     ui_object.validation_message
+                   when :badInput
+                     ui_object.validity?(:badInput)
+                   when :customError
+                     ui_object.validity?(:customError)
+                   when :patternMismatch
+                     ui_object.validity?(:patternMismatch)
+                   when :rangeOverflow
+                     ui_object.validity?(:rangeOverflow)
+                   when :rangeUnderflow
+                     ui_object.validity?(:rangeUnderflow)
+                   when :stepMismatch
+                     ui_object.validity?(:stepMismatch)
+                   when :tooLong
+                     ui_object.validity?(:tooLong)
+                   when :tooShort
+                     ui_object.validity?(:tooShort)
+                   when :typeMismatch
+                     ui_object.validity?(:typeMismatch)
+                   when :valid
+                     ui_object.validity?(:valid)
+                   when :valueMissing
+                     ui_object.validity?(:valueMissing)
                    else
                      if property.is_a?(Hash)
                        property.map do |key, value|
@@ -356,5 +392,6 @@ module TestCentricity
       raise "Expected element '#{expected_element.get_name}' to have focus but found '#{focused_obj[:id]} is focused instead'" unless focused_obj == expected_obj.native
 
       puts "Element '#{expected_element.get_name}' is focused as expected"
-    end  end
+      end
+  end
 end