TestCentricity™ Web
The TestCentricity™ Web core generic framework for desktop and mobile web browser-based app testing implements a Page Object and Data Object Model DSL for use with Cucumber, Capybara (version 3.x), and Selenium-Webdriver (version 4.x).
The TestCentricity™ Web gem supports running automated tests against the following web test targets:
- locally hosted desktop browsers (Firefox, Chrome, Edge, Safari, or IE)
- locally hosted emulated iOS Mobile Safari, Android, Windows Phone, or Blackberry mobile browsers (running within a local instance of Chrome)
- 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)
- cloud hosted desktop (Firefox, Chrome, Safari, IE, or Edge) or mobile (iOS Mobile Safari or Android) web browsers using the following service:
- web portals utilizing JavaScript front end application frameworks like Ember, React, Angular, and GWT
- web pages containing HTML5 Video and Audio objects
What's New
A complete history of bug fixes and new features can be found in the CHANGELOG file.
An example project that demonstrates the implementation of a page object model framework using Cucumber and TestCentricity™ can be found here.
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:
gem 'testcentricity_web'
And then execute:
$ bundle
Or install it yourself as:
$ gem install testcentricity_web
Setup
Using Cucumber
If you are using Cucumber, you need to require the following in your env.rb file:
require 'capybara/cucumber'
require 'testcentricity_web'
Using RSpec
If you are using RSpec instead, you need to require the following in your env.rb file:
require 'capybara'
require 'capybara/rspec'
require 'testcentricity_web'
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:
require 'appium_capybara'
You also need to add this line to your automation project's Gemfile:
gem 'appium_capybara'
And then execute:
$ bundle
PageObjects
The Page Object Model is a test automation pattern that aims to create an abstraction of your web app's User Interface that can be used in tests. A Page Object is an object that represents a single page in your AUT (Application Under Test). Page Objects encapsulate the implementation details of a web page and expose an API that supports interaction with, and validation of the UI elements on the page.
Page Objects makes it easier to maintain automated tests because changes to page UI elements are updated in only one location - in the
Page Object class definition. By adopting a Page Object Model, Cucumber Feature files and step definitions are no longer required to
hold specific information about a page's UI objects, thus minimizing maintenance requirements. If any element on, or property of a page changes
(URL path, text field attributes, button captions, etc.), maintenance is performed in the PageObject
class definition only, typically with
no need to update the affected feature file, scenarios, or step definitions.
Defining a PageObject
Your PageObject
class definitions should be contained within individual .rb
files in the features/support/pages
folder of your
test automation project. You define new PageObjects
as shown below:
class LoginPage < TestCentricity::PageObject
end
class HomePage < TestCentricity::PageObject
end
class RegistrationPage < TestCentricity::PageObject
end
Adding Traits to your PageObject
Web pages typically have names and URLs associated with them. Web pages also typically have a unique object or attribute that, when present, 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
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_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
trait(:page_name) { 'Login' }
trait(:page_url) { '/sign_in' }
trait(:page_locator) { 'body.login-body' }
end
class HomePage < TestCentricity::PageObject
# this page may be referred to as 'Home' or 'Dashboard' page so page_name trait is an Array of Strings
trait(:page_name) { ['Home', 'Dashboard'] }
trait(:page_url) { '/dashboard' }
trait(:page_locator) { 'body.dashboard' }
end
class RegistrationPage < TestCentricity::PageObject
trait(:page_name) { 'Registration' }
trait(:page_url) { '/register' }
trait(:page_locator) { 'body.registration' }
end
Adding UI Elements to your PageObject
Web pages are made up of UI elements like text fields, check boxes, combo boxes, radio buttons, tables, lists, buttons, etc.
UI Elements are added to your PageObject
class definition as shown below:
class LoginPage < TestCentricity::PageObject
trait(:page_name) { 'Login' }
trait(:page_url) { '/sign_in' }
trait(:page_locator) { 'body.login-body' }
# Login page UI elements
textfield :user_id_field, 'input#userName'
textfield :password_field, 'input#password'
:login_button, 'button#login'
checkbox :remember_checkbox, 'input#rememberUser'
label :error_message_label, 'div#statusBar.login-error'
end
class RegistrationPage < TestCentricity::PageObject
trait(:page_name) { 'Registration' }
trait(:page_url) { '/register' }
trait(:page_locator) { 'body.registration' }
# Registration page UI elements
textfields first_name_field: 'input#firstName',
last_name_field: 'input#lastName',
email_field: 'input#email',
phone_number_field: 'input#phone',
address_field: 'input#streetAddress',
city_field: 'input#city',
post_code_field: 'input#postalCode',
password_field: 'input#password',
pword_confirm_field: 'input#passwordConfirmation'
selectlists title_select: 'select#title',
gender_select: 'select#gender',
state_select: 'select#stateProvince'
checkbox :email_opt_in_check, 'input#marketingEmailsOptIn'
:sign_up_button, 'button#registrationSignUp'
end
Adding Methods to your PageObject
It is good practice for your Cucumber step definitions to call high level methods in your your PageObject
instead of directly accessing
and interacting with a page object's UI elements. You can add high level methods to your PageObject
class definition for interacting with
the UI to hide implementation details, as shown below:
class LoginPage < TestCentricity::PageObject
trait(:page_name) { 'Login' }
trait(:page_url) { '/sign_in' }
trait(:page_locator) { 'body.login-body' }
# Login page UI elements
textfield :user_id_field, 'input#userName'
textfield :password_field, 'input#password'
:login_button, 'button#login'
checkbox :remember_checkbox, 'input#rememberUser'
label :error_message_label, 'div#statusBar.login-error'
link :forgot_password_link, 'a.forgotPassword'
# log in to web app
def login(user_id, password)
user_id_field.set(user_id)
password_field.set(password)
.click
end
# set the state of the Remember Me checkbox
def remember_me(state)
remember_checkbox.set_checkbox_state(state)
end
# verify Login page default UI state
def verify_page_ui
ui = {
self => { title: 'Login' },
=> { visible: true, caption: 'LOGIN' },
user_id_field => { visible: true, enabled: true, value: '', placeholder: 'User name' },
password_field => { visible: true, enabled: true, value: '', placeholder: 'Password' },
remember_checkbox => { exists: true, enabled: true, checked: false },
forgot_password_link => { visible: true, caption: 'Forgot your password?' },
=> { visible: false }
}
verify_ui_states(ui)
end
end
class RegistrationPage < TestCentricity::PageObject
trait(:page_name) { 'Registration' }
trait(:page_url) { '/register' }
trait(:page_locator) { 'body.registration' }
# Registration page UI elements
textfields first_name_field: 'input#firstName',
last_name_field: 'input#lastName',
email_field: 'input#email',
phone_number_field: 'input#phone',
address_field: 'input#streetAddress',
city_field: 'input#city',
post_code_field: 'input#postalCode',
password_field: 'input#password',
pword_confirm_field: 'input#passwordConfirmation'
selectlists title_select: 'select#title',
gender_select: 'select#gender',
state_select: 'select#stateProvince'
checkbox :email_opt_in_check, 'input#marketingEmailsOptIn'
sign_up_button: 'button#registrationSignUp',
cancel_button: 'button#registrationCancel'
# populate Registration page fields with profile data
def enter_profile_data(profile)
fields = { title_select => profile.title,
first_name_field => profile.first_name,
last_name_field => profile.last_name,
gender_select => profile.gender,
phone_number_field => profile.phone,
email_field => profile.email,
address_field => profile.address,
city_field => profile.city,
state_select => profile.state,
post_code_field => profile.postal_code,
password_field => profile.password,
pword_confirm_field => profile.confirm_password,
email_opt_in_check => profile.email_opt_in
}
populate_data_fields(fields)
.click
end
end
Once your PageObjects
have been instantiated, you can call your methods as shown below:
login_page.remember_me(true)
login_page.login('snicklefritz', 'Pa55w0rd')
PageSections
A PageSection
is a collection of UI Elements that may appear in multiple locations on a page, or on multiple pages in a web
app. It is a collection of UI Elements that represent a conceptual area of functionality, like a navigation bar, a search capability,
or a menu. UI Elements and functional behavior are confined to the scope of a PageSection
object.
A PageSection
may contain other PageSection
objects.
Defining a PageSection
Your PageSection
class definitions should be contained within individual .rb
files in the features/support/sections
folder of
your test automation project. You define new PageSection
as shown below:
class SearchForm < TestCentricity::PageSection
end
Adding Traits to a PageSection
A PageSection
typically has a root node object that encapsulates a collection of UIElements
. The section_locator
trait
specifies the CSS or Xpath expression that uniquely identifies that root node object.
You define your section's Traits as shown below:
class SearchForm < TestCentricity::PageSection
trait(:section_locator) { 'form#gnav-search' }
trait(:section_name) { 'Search widget' }
end
Adding UI Elements to your PageSection
PageSections
are typically made up of UI elements like text fields, check boxes, combo boxes, radio buttons, tables, lists, buttons, etc.
UI Elements are added to your PageSection
class definition as shown below:
class SearchForm < TestCentricity::PageSection
trait(:section_locator) { 'form#gnav-search' }
trait(:section_name) { 'Search widget' }
# Search Form UI elements
textfield :search_field, 'input#search-query'
:search_button, 'button[type=submit]'
end
Adding Methods to your PageSection
You can add high level methods to your PageSection
class definition, as shown below:
class SearchForm < TestCentricity::PageSection
trait(:section_locator) { 'form#gnav-search' }
trait(:section_name) { 'Search widget' }
# Search Form UI elements
textfield :search_field, 'input#search-query'
:search_button, 'button[type=submit]'
def search_for(value)
search_field.set(value)
.click
end
end
Adding PageSections to your PageObject
You add a PageSection
to its associated PageObject
as shown below:
class HomePage < TestCentricity::PageObject
trait(:page_name) { 'Home' }
trait(:page_url) { '/dashboard' }
trait(:page_locator) { 'body.dashboard' }
# Home page Section Objects
section :search_form, SearchForm
end
Once your PageObject
has been instantiated, you can call its PageSection
methods as shown below:
home_page.search_form.search_for('ocarina')
UIElements
PageObjects
and PageSections
are typically made up of UI Element like text fields, check boxes, select lists (combo boxes),
radio buttons, tables, ordered and unordered lists, buttons, images, HTML5 video objects, HTML5 audio objects, etc. UI Elements are declared
and instantiated within the class definition of the PageObject
or PageSection
in which they are contained. With TestCentricity Web,
all UI elements are based on the UIElement
class.
Declaring and Instantiating UIElements
Single UIElement
declarations have the following format:
elementType :element Name, locator
- The
element name
is the unique name that you will use to refer to the UI element and is specified as aSymbol
. - The
locator
is the CSS or XPath attribute that uniquely and unambiguously identifies theUIElement
.
Multiple UIElement
declarations for a collection of elements of the same type can be performed by passing a hash table containing the
names and locators of each individual element.
Example UIElement Declarations
Supported UIElement
elementTypes and their declarations have the following format:
Single element declarations:
class SamplePage < TestCentricity::PageObject
:button_name, locator
textfield :field_name, locator
checkbox :checkbox_name, locator
radio :radio_button_name, locator
label :label_name, locator
link :link_name, locator
selectlist :select_name, locator
list :list_name, locator
table :table_name, locator
range :range_name, locator
image :image_name, locator
video :video_name, locator
audio :audio_name, locator
filefield :filefield_name, locator
end
Multiple element declarations:
class SamplePage < TestCentricity::PageObject
button_1_name: locator,
button_2_name: locator,
button_X_name: locator
textfields field_1_name: locator,
field_2_name: locator,
field_X_name: locator
checkboxes check_1_name: locator,
check_2_name: locator,
check_X_name: locator
radios radio_1_name: locator,
radio_X_name: locator
labels label_1_name: locator,
label_X_name: locator
links link_1_name: locator,
link_X_name: locator
selectlists selectlist_1_name: locator,
selectlist_X_name: locator
lists list_1_name: locator,
list_X_name: locator
tables table_1_name: locator,
table_X_name: locator
ranges range_1_name: locator,
range_X_name: locator
images image_1_name: locator,
image_X_name: locator
videos video_1_name: locator,
video_X_name: locator
audios audio_1_name: locator,
audio_X_name: locator
filefields filefield_1_name: locator,
filefield_X_name: locator
end
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.
UIElement Inherited Methods
With TestCentricity, all UI elements are based on the UIElement
class, and inherit the following methods:
Action methods:
element.click
element.double_click
element.right_click
element.click_at(x, y)
element.hover
element.hover_at(x, y)
element.scroll_to(position)
element.drag_by(right_offset, down_offset)
element.drag_and_drop(target, right_offset, down_offset)
Object state methods:
element.exists?
element.visible?
element.hidden?
element.enabled?
element.disabled?
element.displayed?
element.obscured?
element.focused?
element.content_editable?
element.get_value
element.count
element.style
element.title
element.width
element.height
element.x
element.y
element.get_attribute(attrib)
element.get_native_attribute(attrib)
element.inspect
Waiting methods:
element.wait_until_exists(seconds)
element.wait_until_gone(seconds)
element.wait_until_visible(seconds)
element.wait_until_hidden(seconds)
element.wait_until_value_is(value, seconds)
element.wait_until_value_changes(seconds)
WAI-ARIA Object Accessibility (A11y) methods:
element.role
element.tabindex
element.aria_disabled?
element.aria_hidden?
element.
element.aria_required?
element.aria_invalid?
element.aria_checked?
element.aria_readonly?
element.aria_haspopup?
element.aria_selected?
element.aria_pressed?
element.aria_label
element.aria_labelledby
element.aria_describedby
element.aria_live
element.aria_sort
element.aria_rowcount
element.aria_colcount
element.aria_valuemax
element.aria_valuemin
element.aria_valuenow
element.aria_valuetext
element.aria_orientation
element.aria_roledescription
element.aria_autocomplete
element.aria_controls
element.aria_modal?
element.aria_keyshortcuts
element.aria_multiline?
element.aria_multiselectable?
element.aria_busy?
Populating your PageObject or PageSection with data
A typical automated test may be required to perform the entry of test data by interacting with various UIElements
on your PageObject
or
PageSection
. This data entry can be performed using the various object action methods (listed above) for each UIElement
that needs to be
interacted with.
The PageObject.populate_data_fields
and PageSection.populate_data_fields
methods support the entry of test data into a collection of
UIElements
. The populate_data_fields
method accepts a hash containing key/hash pairs of UIElements
and their associated data to be
entered. Data values must be in the form of a String
for textfield
and selectlist
controls. For checkbox
and radio
controls, data
must either be a Boolean
or a String
that evaluates to a Boolean
value (Yes, No, 1, 0, true, false). For section
objects, data values
must be a String
, and the section
object must have a set
method defined.
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 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.
def enter_data(user_data)
fields = {
first_name_field => user_data.first_name,
last_name_field => user_data.last_name,
email_field => user_data.email,
country_code_select => user_data.country_code,
phone_number_field => user_data.phone_number,
time_zone_select => user_data.time_zone,
language_select => user_data.language
}
populate_data_fields(fields, wait_time = 2)
end
Verifying UIElements on your PageObject or PageSection
A typical automated test executes one or more interactions with the user interface, and then performs a validation to verify whether
the expected state of the UI has been achieved. This verification can be performed using the various object state methods (listed above)
for each UIElement
that requires verification. Depending on the complexity and number of UIElements
to be verified, the code required to
verify the presence of UIElements
and their correct states can become cumbersome.
The PageObject.verify_ui_states
and PageSection.verify_ui_states
methods support the verification of multiple properties of multiple
UI elements on a PageObject
or PageSection
. The verify_ui_states
method accepts a hash containing key/hash pairs of UI
elements and their properties or attributes to be verified.
ui = {
object1 => { property: state },
object2 => { property: state, property: state },
object3 => { property: state }
}
verify_ui_states(ui)
The verify_ui_states
method queues up any exceptions that occur while verifying each object's properties until all UIElements
and their
properties have been checked, and then posts any exceptions encountered upon completion. Posted exceptions include a screenshot with a red
dashed highlight around the UI element that did not match the expected results.
The verify_ui_states
method supports the following property/state pairs:
All Objects:
:exists Boolean
:enabled Boolean
:disabled Boolean
:visible Boolean
:hidden Boolean
:displayed Boolean
:width Integer
:height Integer
:x Integer
:y Integer
:class String
:value or :caption String
:attribute Hash
Text Fields:
:readonly Boolean
:placeholder String
:maxlength Integer
:min Integer
:max Integer
:step Integer
Checkboxes:
:checked Boolean
Radio Buttons:
:selected Boolean
Images
:loaded Boolean
:broken Boolean
:src String
:alt String
Lists
:items Array of Strings
:itemcount Integer
:item Hash
:selected String
Select Lists (ComboBoxes):
:items or :options Array of Strings
:itemcount or :optioncount Integer
:selected String
Tables
:rowcount Integer
:columncount Integer
:columnheaders Array of String
:cell Hash
:row Hash
:column Hash
Audio/Video Media Objects
:autoplay Boolean
:ended Boolean
:controls Boolean
:loop Boolean
:muted Boolean
:default_muted Boolean
:paused Boolean
:seeking Boolean
:src String
:current_time Float
:default_playback_rate Float
:duration Float
:playback_rate Float
:ready_state Integer
:volume Float
:crossorigin String
:preload String
:poster String
ARIA accessibility property/state pairs
The verify_ui_states
method supports the following ARIA accessibility property/state pairs:
All Objects:
:aria_label String
:aria_disabled Boolean
:aria_labelledby String
:aria_describedby String
:aria_live Boolean
:aria_selected Boolean
:aria_hidden Boolean
:aria_expanded Boolean
:aria_required Boolean
:aria_invalid Boolean
:aria_checked Boolean
:aria_readonly Boolean
:aria_pressed Boolean
:aria_haspopup Boolean
:aria_sort String
:aria_rowcount String
:aria_colcount String
:aria_valuemax String
:aria_valuemin String
:aria_valuenow String
:aria_valuetext String
:aria_orientation String
:aria_keyshortcuts String
:aria_roledescription String
:aria_autocomplete String
:aria_controls String
:aria_modal String
:aria_multiline Boolean
:aria_multiselectable Boolean
:content_editable Boolean
Comparison States
The verify_ui_states
method supports comparison states using property/comparison state pairs:
object => { property: { comparison_state: value } }
Comparison States:
:lt or :less_than Integer or String
:lt_eq or :less_than_or_equal Integer or String
:gt or :greater_than Integer or String
:gt_eq or :greater_than_or_equal Integer or String
:starts_with String
:ends_with String
:contains String
:not_contains or :does_not_contain Integer or String
:not_equal Integer, String, or Boolean
The example below depicts a verify_changes_saved
method that uses the verify_ui_states
method to verify that all expected
values appear in the associated text fields after entering data and performing a save operation.
def verify_changes_saved
# verify saved user data is correctly displayed
ui = {
first_name_field => { visible: true, aria_invalid: false, value: User.current.first_name },
last_name_field => { visible: true, aria_invalid: false, value: User.current.last_name },
email_field => { visible: true, aria_invalid: false, value: User.current.email },
phone_number_field => { visible: true, aria_invalid: false, value: User.current.phone_number },
time_zone_select => { visible: true, aria_invalid: false, value: User.current.time_zone },
language_select => { visible: true, aria_invalid: false, value: User.current.language },
avatar_container => { visible: true },
avatar_image => { visible: true, broken: false, src: { contains: User.current.avatar_file_name } },
=> { visible: false }
}
verify_ui_states(ui)
# verify avatar src url does not contain /null/ institution id
verify_ui_states(avatar_image => { src: { does_not_contain: "/null/" } })
end
I18n Translation Validation
The verify_ui_states
method also supports I18n string translations using property/I18n key name pairs:
object => { property: { translate_key: 'name of key in I18n compatible .yml file' } }
I18n Translation Keys:
:translate String
:translate_upcase String
:translate_downcase String
:translate_capitalize String
:translate_titlecase String
The example below depicts the usage of the verify_ui_states
method to verify that the captions for menu items are correctly
translated.
def
ui = {
account_settings_item => { visible: true, caption: { translate: 'Header.settings.account' } },
help_item => { visible: true, caption: { translate: 'Header.settings.help' } },
feedback_item => { visible: true, caption: { translate: 'Header.settings.feedback' } },
legal_item => { visible: true, caption: { translate: 'Header.settings.legal' } },
institution_item => { visible: true, caption: { translate: 'Header.settings.institution' } },
configurations_item => { visible: true, caption: { translate: 'Header.settings.configurations' } },
contact_us_item => { visible: true, caption: { translate: 'Header.settings.contact' } },
downloads_item => { visible: true, caption: { translate: 'Header.settings.downloads' } }
}
verify_ui_states(ui)
end
Each supported language/locale combination has a corresponding .yml
file. I18n .yml
file naming convention uses
ISO-639 language codes and ISO-3166 country codes. For example:
Language (Country) | File name |
---|---|
English | en.yml |
English (Canada) | en-CA.yml |
French (Canada) | fr-CA.yml |
French | fr.yml |
Spanish | es.yml |
German | de.yml |
Portuguese (Brazil) | pt-BR.yml |
Portuguese (Portugal) | pt-PT.yml |
I18n .yml
files contain key/value pairs representing the name of a translated string (key) and the string value.
Baseline translation strings are stored in .yml
files in the config/locales/
folder.
my_automation_project
├── config
│ ├── locales
│ │ ├── en.yml
│ │ ├── es.yml
│ │ ├── fr.yml
│ │ ├── fr-CA.yml
│ │ └── en-AU.yml
│ ├── test_data
│ └── cucumber.yml
├── downloads
├── features
├── Gemfile
└── README.md
Instantiating your PageObjects
Before you can call the methods in your PageObjects
and PageSections
, you must instantiate the PageObjects
of your web
application, as well as create instance variables which can be used when calling a PageObject
's methods from your step definitions.
There are several ways to instantiate your PageObjects
.
One common implementation is shown below:
module WorldPages
def login_page
@login_page ||= LoginPage.new
end
def home_page
@home_page ||= HomePage.new
end
def registration_page
@registration_page ||= RegistrationPage.new
end
def search_results_page
@search_results_page ||= SearchResultsPage.new
end
end
World(WorldPages)
The WorldPages
module above can be defined in your env.rb
file, or you can define it in a separate world_pages.rb
file in the
features/support
folder.
While this approach is effective for small web applications with only a few pages (and hence few PageObjects
), it quickly becomes
cumbersome to manage if your web application has dozens of PageObjects
that need to be instantiated and managed.
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
instantiated by PageManager
:
module WorldPages
def page_objects
{
login_page: LoginPage,
home_page: HomePage,
registration_page: RegistrationPage,
search_results_page: SearchResultsPage,
products_grid_page: ProductsCollectionPage,
product_detail_page: ProductDetailPage,
shopping_basket_page: ShoppingBasketPage,
payment_method_page: PaymentMethodPage,
confirm_purchase_page: PurchaseConfirmationPage,
my_account_page: MyAccountPage,
my_order_history_page: MyOrderHistoryPage,
my_ship_to_addresses_page: MyShipToAddressesPage,
terms_conditions_page: TermsConditionsPage,
privacy_policy_page: PrivacyPolicyPage,
faqs_page: FAQsPage,
contact_us_page: ContactUsPage
}
end
end
World(WorldPages)
The WorldPages
module above should be defined in the world_pages.rb
file in the features/support
folder.
Include the code below in your env.rb
file to ensure that your PageObjects
are instantiated before your Cucumber scenarios are
executed:
include WorldPages
WorldPages.instantiate_page_objects
NOTE: If you intend to use the PageManager
, you must define a page_name
trait for each of the PageObjects
to be registered.
Leveraging the PageManager in your Cucumber tests
Many Cucumber based automated tests suites include scenarios that verify that web pages are correctly loaded, displayed, or can be navigated to by clicking associated links. One such Cucumber navigation scenario is displayed below:
Scenario Outline: Verify Home page navigation links
Given I am on the Home page
When I click the <page name> navigation link
Then I expect the <page name> page to be correctly displayed
Examples:
|page name |
|Registration |
|My Account |
|Terms & Conditions |
|Privacy Policy |
|FAQs |
|Contact Us |
In the above example, the step definitions associated with the 3 steps might be implemented using a page_dispatcher
method using a
case
statement to parse the page
parameter as in the example below:
Given(/^I am on the (.*) page$/) do |page_name|
target_page = page_dispatcher(page_name)
target_page.load_page
end
When(/^I click the (.*) navigation link$/) do |link_name|
target_page = page_dispatcher(link_name)
target_page.navigate_to
end
Then(/^I expect the (.*) page to be correctly displayed$/) do |page_name|
target_page = page_dispatcher(page_name)
target_page.verify_page_exists
target_page.verify_page_ui
end
# this method takes a page name as a parameter and returns an instance of the associated Page Object
def page_dispatcher(page_name)
page = case page_name
when 'Registration'
registration_page
when 'My Account'
my_account_page
when 'Terms & Conditions'
terms_conditions_page
when 'Privacy Policy'
privacy_policy_page
when 'Contact Us'
contact_us_page
when 'FAQs'
faqs_page
end
raise "No page object defined for page named '#{page_name}'" unless page
page
end
While this approach may be effective for small web applications with only a few pages (and hence few PageObjects
), it quickly becomes
cumbersome to manage if your web application has dozens of PageObjects
that need to be managed.
The PageManager
class provides a find_page
method that replaces the cumbersome and difficult to maintain case
statement used in the
above example. The PageManager.current_page
method allows you to set or get an instance of the currently active Page Object.
To use these PageManager
methods, include the step definitions and code below in a page_steps.rb
or generic_steps.rb
file in the
features/step_definitions
folder:
include TestCentricity
Given(/^I am on the (.*) page$/) do |page_name|
target_page = PageManager.find_page(page_name)
target_page.load_page
end
When(/^I click the (.*) navigation link$/) do |page_name|
target_page = PageManager.find_page(page_name)
target_page.navigate_to
end
Then(/^I expect to see the (.*) page$/) do |page_name|
target_page = PageManager.find_page(page_name)
target_page.verify_page_exists
end
Then(/^I expect the (.*) page to be correctly displayed$/) do |page_name|
target_page = PageManager.find_page(page_name)
target_page.verify_page_exists
target_page.verify_page_ui
end
Connecting to a Web Browser
The TestCentricity::WebDriverConnect.initialize_web_driver
method configures the appropriate Selenium-Webdriver capabilities required to
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.
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
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 |
ie |
Windows only (IE version 10.x or greater only) |
Refer to section 8.7 (Using Browser specific Profiles in cucumber.yml) below.
Setting desktop browser window size
To set the size of a desktop browser window, you set the BROWSER_SIZE
Environment Variable to the desired width and height in pixels as shown below:
BROWSER_SIZE=1600,1000
To maximize a desktop browser window, you set the BROWSER_SIZE
Environment Variable to 'max' as shown below:
BROWSER_SIZE=max
Testing file downloads with desktop browsers
File download functionality can be tested with locally hosted instances of Chrome, Edge, or Firefox desktop browsers. Your automation project must include
a /downloads
folder at the same level as the /config
and /features
folders, as depicted below:
my_automation_project
├── config
├── downloads
├── features
├── Gemfile
└── README.md
When running tests in multiple concurrent threads using the parallel_tests
gem, a new folder will be created within the /downloads
folder for each
test thread. This is to ensure that files downloaded in each test thread are isolated from tests running in other parallel threads. An example of the
/downloads
folder structure for 4 parallel threads is depicted below:
my_automation_project
├── config
├── downloads
│ ├── 1
│ ├── 2
│ ├── 3
│ └── 4
├── features
├── Gemfile
└── README.md
When testing file downloads using a local instance of Firefox, you will need to specify the MIME types of the various file types that your tests will
be downloading. This is accomplished by setting the MIME_TYPES
Environment Variable to a comma-delimited string containing the list of MIME types to
be accepted. This list is required as it will prevent Firefox from displaying the File Download modal dialog, which will halt your automated tests. An
example of a list of MIME types is depicted below:
MIME_TYPES='images/jpeg, application/pdf, application/octet-stream'
A detailed list of file MIME types can be found here
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
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:
WEB_BROWSER |
HOST_BROWSER |
CSS Screen Dimensions | Default Orientation | OS Version |
---|---|---|---|---|
ipad |
chrome |
1024 x 768 | landscape | iOS 12 |
ipad_pro |
chrome |
1366 x 1024 | landscape | iOS 12 |
ipad_pro_10_5 |
chrome |
1112 x 834 | landscape | iOS 12.2 |
ipad_pro_11 |
chrome |
1194 x 834 | landscape | iOS 12.2 |
ipad_pro_12_9 |
chrome |
1366 x 1024 | landscape | iOS 13.1 |
ipad_chrome |
chrome |
1024 x 768 | landscape | iOS 12.2 - Mobile Chrome browser for iOS |
ipad_firefox |
chrome |
1024 x 768 | landscape | iOS 12.2 - Mobile Firefox browser for iOS |
ipad_edge |
chrome |
1024 x 768 | landscape | iOS 12.2 - Mobile Edge browser for iOS |
kindle_fire |
chrome |
1024 x 600 | landscape | |
kindle_firehd7 |
chrome |
800 x 480 | landscape | Fire OS 3 |
kindle_firehd8 |
chrome |
1280 x 800 | landscape | Fire OS 5 |
kindle_firehd10 |
chrome |
1920 x 1200 | landscape | Fire OS 5 |
surface |
chrome |
1366 x 768 | landscape | |
blackberry_playbook |
chrome |
1024 x 600 | landscape | BlackBerry Tablet OS |
samsung_galaxy_tab |
chrome |
1280 x 800 | landscape | Android 4.0.4 |
google_nexus7 |
chrome |
960 x 600 | landscape | Android 4.4.4 |
google_nexus9 |
chrome |
1024 x 768 | landscape | Android 5.1 |
google_nexus10 |
chrome |
1280 x 800 | landscape | Android 5.1 |
iphone6 |
chrome |
375 x 667 | portrait | iOS 12 |
iphone6_plus |
chrome |
414 x 736 | portrait | iOS 12 |
iphone7 |
chrome |
375 x 667 | portrait | iOS 12 |
iphone7_plus |
chrome |
414 x 736 | portrait | iOS 12 |
iphone7_chrome |
chrome |
375 x 667 | portrait | iOS 12.2 - Mobile Chrome browser for iOS |
iphone7_firefox |
chrome |
375 x 667 | portrait | iOS 12.2 - Mobile Firefox browser for iOS |
iphone7_edge |
chrome |
375 x 667 | portrait | iOS 12.2 - Microsoft Edge browser for iOS |
iphone8 |
chrome |
375 x 667 | portrait | iOS 12 |
iphone8_plus |
chrome |
414 x 736 | portrait | iOS 12 |
iphone_x |
chrome |
375 x 812 | portrait | iOS 12.2 |
iphone_xr |
chrome |
414 x 896 | portrait | iOS 12.2 |
iphone_xs |
chrome |
375 x 812 | portrait | iOS 12.2 |
iphone_xs_max |
chrome |
414 x 896 | portrait | iOS 12.2 |
iphone_11 |
chrome |
414 x 896 | portrait | iOS 13.1 |
iphone_11_pro |
chrome |
375 x 812 | portrait | iOS 13.1 |
iphone_11_pro_max |
chrome |
414 x 896 | portrait | iOS 13.1 |
nexus6 |
chrome |
411 x 731 | portrait | Android 6 |
pixel |
chrome |
411 x 731 | portrait | Android 8 |
pixel_xl |
chrome |
411 x 731 | portrait | Android 8 |
samsung_galaxy_s4 |
chrome |
360 x 640 | portrait | Android 5.0.1 |
samsung_galaxy_s5 |
chrome |
360 x 640 | portrait | Android 6.0.1 |
samsung_galaxy_s6 |
chrome |
360 x 640 | portrait | Android 6.0.1 |
windows_phone7 |
chrome |
320 x 480 | portrait | Windows Phone OS 7.5 |
windows_phone8 |
chrome |
320 x 480 | portrait | Windows Phone OS 8.0 |
lumia_950_xl |
chrome |
360 x 640 | portrait | Windows Phone OS 10 |
blackberry_z10 |
chrome |
384 x 640 | portrait | BlackBerry 10 OS |
blackberry_z30 |
chrome |
360 x 640 | portrait | BlackBerry 10 OS |
blackberry_leap |
chrome |
360 x 640 | portrait | BlackBerry 10 OS |
blackberry_passport |
chrome |
504 x 504 | square | BlackBerry 10 OS |
To change the emulated device's screen orientation from the default setting, set the ORIENTATION
Environment Variable to either portrait
or landscape
.
To use a local instance of the Chrome desktop browser to host the emulated mobile web browser, you must set the HOST_BROWSER
Environment Variable
to chrome
.
Refer to section 8.7 (Using Browser specific Profiles in cucumber.yml) below.
User defined mobile device profiles
User defined mobile device profiles can be specified in a device.yml
file for testing locally hosted emulated mobile web browsers running in an instance
of the Chrome desktop browser. The user specified device profiles must be located at config/data/devices/devices.yml
as depicted below:
my_automation_project
├── config
│ ├── data
│ │ └── devices
│ │ └── devices.yml
│ ├── locales
│ ├── test_data
│ └── cucumber.yml
├── downloads
├── features
├── Gemfile
└── README.md
The format for a new device profile is:
:new_device_profile:
:name: "New Device Name"
:os: (ios, android, kindle, or blackberry)
:type: (phone or tablet)
:css_width: css width in pixels
:css_height: css height in pixels
:default_orientation: (portrait or landscape)
:user_agent: "user agent string"
Selenium Grid 4 and Dockerized Selenium Grid 4 hosted desktop and emulated mobile web browsers
For remote desktop and emulated mobile web browsers running on Selenium Grid 4 or Dockerized Selenium Grid 4 environments as described in the table below.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to one of the following desktop browsers - chrome , chrome_headless , edge , edge_headless , or firefox , or any of the mobile web browsers described above. |
SELENIUM |
Must be set to remote |
REMOTE_ENDPOINT |
Must be set to the URL of the Grid hub, which is usually http://localhost:4444/wd/hub |
Refer to section 8.7 (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
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. The Appium server must be running prior to invoking Cucumber to run your features/scenarios.
Once your test environment is properly configured, the following Environment Variables must be set as described in the table below.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to appium |
APP_PLATFORM_NAME |
Must be set to iOS |
APP_BROWSER |
Must be set to Safari |
APP_VERSION |
Must be set to 15.2 , 14.5 , or which ever iOS version you wish to run within the XCode Simulator |
APP_DEVICE |
Set to iOS device name supported by the iOS Simulator (iPhone 13 Pro Max , iPad Pro (12.9-inch) (5th generation) , etc.) or name of physically connected iOS device |
DEVICE_TYPE |
Must be set to phone or tablet |
APP_UDID |
UDID of physically connected iOS device (not used for simulators) |
TEAM_ID |
unique 10-character Apple developer team identifier string (not used for simulators) |
TEAM_NAME |
String representing a signing certificate (not used for simulators) |
APP_ALLOW_POPUPS |
[Optional] Allow javascript to open new windows in Safari. Set to true or false |
APP_IGNORE_FRAUD_WARNING |
[Optional] Prevent Safari from showing a fraudulent website warning. Set to true or false |
APP_NO_RESET |
[Optional] Don't reset app state after each test. Set to true or false |
APP_FULL_RESET |
[Optional] Perform a complete reset. Set to true or false |
APP_INITIAL_URL |
[Optional] Initial URL, default is a local welcome page. e.g. http://www.apple.com |
WDA_LOCAL_PORT |
[Optional] Used to forward traffic from Mac host to real iOS devices over USB. Default value is same as port number used by WDA on device. |
LOCALE |
[Optional] Locale to set for the simulator. e.g. fr_CA |
LANGUAGE |
[Optional] Language to set for the simulator. e.g. fr |
ORIENTATION |
[Optional] Set to portrait or landscape (only for iOS simulators) |
NEW_COMMAND_TIMEOUT |
[Optional] Time (in Seconds) that Appium will wait for a new command from the client |
SHOW_SIM_KEYBOARD |
[Optional] Show the simulator keyboard during text entry. Set to true or false |
SHUTDOWN_OTHER_SIMS |
[Optional] Close any other running simulators. Set to true or false . See note below. |
The SHUTDOWN_OTHER_SIMS
environment variable can only be set if you are running Appium Server with the --relaxed-security
or
--allow-insecure=shutdown_other_sims
arguments passed when starting it from the command line, or when running the server from the
Appium Server GUI app. A security violation error will occur without relaxed secutity enabled.
Refer to section 8.7 (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
must install Android Studio, the desired Android version-specific virtual device emulators, and Appium. Refer to this page
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.
The Appium server must be running prior to invoking Cucumber to run your features/scenarios. Refer to this page for information on configuring Appium to use the correct version of Chromedriver required to work with the web browser supported by each Android OS version.
Once your test environment is properly configured, the following Environment Variables must be set as described in the table below.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to appium |
APP_PLATFORM_NAME |
Must be set to Android |
APP_BROWSER |
Must be set to Chrome or Browser |
APP_VERSION |
Must be set to 8.0 , 7.0 , or which ever Android OS version you wish to run with the Android Virtual Device |
APP_DEVICE |
Set to Android Virtual Device ID (Pixel_2_XL_API_26 , Nexus_6_API_23 , etc.) found in Advanced Settings of AVD Configuration |
DEVICE_TYPE |
Must be set to phone or tablet |
ORIENTATION |
[Optional] Set to portrait or landscape |
APP_INITIAL_URL |
[Optional] Initial URL, default is a local welcome page. e.g. http://www.apple.com |
APP_NO_RESET |
[Optional] Don't reset app state after each test. Set to true or false |
APP_FULL_RESET |
[Optional] Perform a complete reset. Set to true or false |
LOCALE |
[Optional] Locale to set for the simulator. e.g. fr_CA |
LANGUAGE |
[Optional] Language to set for the simulator. e.g. fr |
NEW_COMMAND_TIMEOUT |
[Optional] Time (in Seconds) that Appium will wait for a new command from the client |
CHROMEDRIVER_EXECUTABLE |
[Optional] Absolute local path to webdriver executable |
Refer to section 8.7 (Using Browser specific Profiles in cucumber.yml) below.
Remotely hosted desktop and mobile web browsers
You can run your automated tests against remotely hosted desktop and mobile web browsers using the BrowserStack, SauceLabs, TestingBot, or
LambdaTest services. If your tests are running against a web site hosted on your local computer (localhost
), or on a staging server inside
your LAN, you must set the TUNNELING
Environment Variable to true
.
Refer to section 8.7 (Using Browser specific Profiles in cucumber.yml) below.
Remote desktop browsers on the BrowserStack service
For remotely hosted desktop web browsers on the BrowserStack service, the following Environment Variables must be set as described in the table below. Refer to the Browserstack-specific capabilities chart page for information regarding the specific capabilities.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to browserstack |
BS_USERNAME |
Must be set to your BrowserStack account user name |
BS_AUTHKEY |
Must be set to your BrowserStack account access key |
BS_OS |
Must be set to OS X or Windows |
BS_OS_VERSION |
Refer to os_version capability in chart |
BS_BROWSER |
Refer to browser capability in chart |
BS_VERSION |
[Optional] Refer to browser_version capability in chart. If not specified, latest stable version of browser will be used. |
TUNNELING |
Must be true if you are testing against internal/local servers (true or false ). If true , the BrowserStack Local instance will be automatically started. |
RESOLUTION |
[Optional] Refer to supported screen resolution capability in chart |
RECORD_VIDEO |
[Optional] Enable screen video recording during test execution (true or false ) |
TIME_ZONE |
[Optional] Specify custom time zone. Refer to browserstack.timezone capability in chart |
IP_GEOLOCATION |
[Optional] Specify IP Geolocation. Refer to IP Geolocation to select a country code. |
ALLOW_POPUPS |
[Optional] Allow popups (true or false ) - for Safari, IE, and Edge browsers only |
ALLOW_COOKIES |
[Optional] Allow all cookies (true or false ) - for Safari browsers only |
SCREENSHOTS |
[Optional] Generate screenshots for debugging (true or false ) |
NETWORK_LOGS |
[Optional] Capture network logs (true or false ) |
If the BrowserStack Local instance is running (TUNNELING
Environment Variable is true
), call theTestCentricity::WebDriverConnect.close_tunnel
method
upon completion of your test suite to stop the Local instance. Place the code shown below in your env.rb
or hooks.rb
file.
# code to stop BrowserStack Local instance after end of test (if tunneling is enabled)
at_exit do
TestCentricity::WebDriverConnect.close_tunnel if Environ.tunneling
end
Remote mobile browsers on the BrowserStack service
For remotely hosted mobile web browsers on the BrowserStack service, the following Environment Variables must be set as described in the table below. Refer to the Browserstack-specific capabilities chart page for information regarding the specific capabilities.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to browserstack |
BS_USERNAME |
Must be set to your BrowserStack account user name |
BS_AUTHKEY |
Must be set to your BrowserStack account access key |
BS_OS |
Must be set to ios or android |
BS_BROWSER |
Must be set to Safari (for iOS) or Chrome (for Android) |
BS_DEVICE |
Refer to device capability in chart |
BS_REAL_MOBILE |
Set to true if running against a real device |
DEVICE_TYPE |
Must be set to phone or tablet |
TUNNELING |
Must be true if you are testing against internal/local servers (true or false ). If true , the BrowserStack Local instance will be automatically started. |
ORIENTATION |
[Optional] Set to portrait or landscape |
RECORD_VIDEO |
[Optional] Enable screen video recording during test execution (true or false ) |
TIME_ZONE |
[Optional] Specify custom time zone. Refer to browserstack.timezone capability in chart |
IP_GEOLOCATION |
[Optional] Specify IP Geolocation. Refer to IP Geolocation to select a country code. |
SCREENSHOTS |
[Optional] Generate screenshots for debugging (true or false ) |
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 table below. Use the Selenium API on the Platform Configurator page to obtain information regarding the specific capabilities.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to saucelabs |
SL_USERNAME |
Must be set to your Sauce Labs account user name or email address |
SL_AUTHKEY |
Must be set to your Sauce Labs account access key |
DATA_CENTER |
Must be set to your Sauce Labs account Data Center assignment (us-west-1 , eu-central-1 , apac-southeast-1 ) |
SL_OS |
Refer to platform capability in the Copy Code section of the Platform Configurator page |
SL_BROWSER |
Must be set to chrome , firefox , safari , internet explorer , or edge |
SL_VERSION |
Refer to version capability in the Copy Code section of the Platform Configurator page |
RESOLUTION |
[Optional] Refer to supported screenResolution capability in the Copy Code section of the Platform Configurator page |
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 the table below. Refer to the TestingBot List of Available Browsers page for information regarding the specific capabilities.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to testingbot |
TB_USERNAME |
Must be set to your TestingBot account user name |
TB_AUTHKEY |
Must be set to your TestingBot account access key |
TB_OS |
Refer to platform capability in chart |
TB_BROWSER |
Refer to browserName capability in chart |
TB_VERSION |
Refer to version capability in chart |
TUNNELING |
Must be true if you are testing against internal/local servers (true or false ) |
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 below. Use the Configuration Wizard on the Selenium Desired Capabilities Generator to obtain information regarding the specific capabilities.
Environment Variable | Description |
---|---|
WEB_BROWSER |
Must be set to lambdatest |
LT_USERNAME |
Must be set to your LambdaTest account user name or email address |
LT_AUTHKEY |
Must be set to your LambdaTest account access key |
LT_OS |
Refer to platform capability in the sample script of the Wizard |
LT_BROWSER |
Refer to browserName capability in the sample script of the Wizard |
LT_VERSION |
Refer to version capability in chart |
RESOLUTION |
[Optional] Refer to supported resolution capability in the sample script of the Wizard |
BROWSER_SIZE |
[Optional] Specify width, height of browser window |
RECORD_VIDEO |
[Optional] Enable screen video recording during test execution (true or false ) |
ALLOW_POPUPS |
[Optional] Allow popups (true or false ) - for Safari, IE, and Edge browsers only |
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
target web browsers is to create browser specific Profiles that set the appropriate Environment Variables for each target browser
in your cucumber.yml
file.
Below is a list of Cucumber Profiles for supported locally and remotely hosted desktop and mobile web browsers (put these in in your
cucumber.yml
file). Before you can use the BrowserStack, SauceLabs, TestingBot or LambdaTest services, you will need to replace the
INSERT USER NAME HERE and INSERT PASSWORD HERE placeholder text with your user account and authorization code for the cloud service(s)
that you intend to connect with.
<% desktop = "--tags @desktop --require features BROWSER_TILE=true BROWSER_SIZE=1500,1000" %>
<% tablet = "--tags @desktop --require features BROWSER_TILE=true" %>
<% mobile = "--tags @mobile --require features BROWSER_TILE=true" %>
#==============
# profiles for locally hosted desktop web browsers
#==============
firefox: WEB_BROWSER=firefox <%= desktop %>
chrome: WEB_BROWSER=chrome <%= desktop %>
edge: WEB_BROWSER=edge <%= desktop %>
safari: WEB_BROWSER=safari <%= desktop %>
ie: WEB_BROWSER=ie <%= desktop %>
firefox_headless: WEB_BROWSER=firefox_headless <%= desktop %>
chrome_headless: WEB_BROWSER=chrome_headless <%= desktop %>
edge_headless: WEB_BROWSER=edge_headless <%= desktop %>
#==============
# profile for Selenium Grid and Dockerized Selenium Grid hosted desktop web browsers
#==============
grid: SELENIUM=remote REMOTE_ENDPOINT="http://localhost:4444/wd/hub"
#==============
# profiles for locally hosted mobile web browsers (emulated locally in Chrome browser)
#==============
ipad: WEB_BROWSER=ipad HOST_BROWSER=chrome <%= tablet %>
ipad_pro: WEB_BROWSER=ipad_pro HOST_BROWSER=chrome <%= tablet %>
ipad_pro_10_5: WEB_BROWSER=ipad_pro_10_5 HOST_BROWSER=chrome <%= tablet %>
ipad_pro_11: WEB_BROWSER=ipad_pro_11 HOST_BROWSER=chrome <%= tablet %>
ipad_pro_12_9: WEB_BROWSER=ipad_pro_12_9 HOST_BROWSER=chrome <%= tablet %>
ipad_chrome: WEB_BROWSER=ipad_chrome HOST_BROWSER=chrome <%= tablet %>
ipad_firefox: WEB_BROWSER=ipad_firefox HOST_BROWSER=chrome <%= tablet %>
ipad_edge: WEB_BROWSER=ipad_edge HOST_BROWSER=chrome <%= tablet %>
iphone6: WEB_BROWSER=iphone6 HOST_BROWSER=chrome <%= mobile %>
iphone6_plus: WEB_BROWSER=iphone6_plus HOST_BROWSER=chrome <%= mobile %>
iphone7: WEB_BROWSER=iphone7 HOST_BROWSER=chrome <%= mobile %>
iphone7_plus: WEB_BROWSER=iphone7_plus HOST_BROWSER=chrome <%= mobile %>
iphone7_chrome: WEB_BROWSER=iphone7_chrome HOST_BROWSER=chrome <%= mobile %>
iphone7_firefox: WEB_BROWSER=iphone7_firefox HOST_BROWSER=chrome <%= mobile %>
iphone7_edge: WEB_BROWSER=iphone7_edge HOST_BROWSER=chrome <%= mobile %>
iphone8: WEB_BROWSER=iphone8 HOST_BROWSER=chrome <%= mobile %>
iphone8_plus: WEB_BROWSER=iphone8_plus HOST_BROWSER=chrome <%= mobile %>
iphone_x: WEB_BROWSER=iphone_x HOST_BROWSER=chrome <%= mobile %>
iphone_xr: WEB_BROWSER=iphone_xr HOST_BROWSER=chrome <%= mobile %>
iphone_xr_chrome: WEB_BROWSER=iphone_xr_chrome HOST_BROWSER=chrome <%= mobile %>
iphone_xr_firefox: WEB_BROWSER=iphone_xr_firefox HOST_BROWSER=chrome <%= mobile %>
iphone_xr_edge: WEB_BROWSER=iphone_xr_edge HOST_BROWSER=chrome <%= mobile %>
iphone_xs: WEB_BROWSER=iphone_xs HOST_BROWSER=chrome <%= mobile %>
iphone_xs_max: WEB_BROWSER=iphone_xs_max HOST_BROWSER=chrome <%= mobile %>
iphone_11: WEB_BROWSER=iphone_11 HOST_BROWSER=chrome <%= mobile %>
iphone_11_pro: WEB_BROWSER=iphone_11_pro HOST_BROWSER=chrome <%= mobile %>
iphone_11_pro_max: WEB_BROWSER=iphone_11_pro_max HOST_BROWSER=chrome <%= mobile %>
nexus6: WEB_BROWSER=nexus6 HOST_BROWSER=chrome <%= mobile %>
kindle_fire: WEB_BROWSER=kindle_fire HOST_BROWSER=chrome <%= tablet %>
kindle_firehd7: WEB_BROWSER=kindle_firehd7 HOST_BROWSER=chrome <%= tablet %>
kindle_firehd8: WEB_BROWSER=kindle_firehd8 HOST_BROWSER=chrome <%= tablet %>
kindle_firehd10: WEB_BROWSER=kindle_firehd10 HOST_BROWSER=chrome <%= tablet %>
surface: WEB_BROWSER=surface HOST_BROWSER=chrome <%= tablet %>
blackberry_playbook: WEB_BROWSER=blackberry_playbook HOST_BROWSER=chrome <%= tablet %>
samsung_galaxy_tab: WEB_BROWSER=samsung_galaxy_tab HOST_BROWSER=chrome <%= tablet %>
google_nexus7: WEB_BROWSER=google_nexus7 HOST_BROWSER=chrome <%= tablet %>
google_nexus9: WEB_BROWSER=google_nexus9 HOST_BROWSER=chrome <%= tablet %>
google_nexus10: WEB_BROWSER=google_nexus10 HOST_BROWSER=chrome <%= tablet %>
samsung_galaxy_s4: WEB_BROWSER=samsung_galaxy_s4 HOST_BROWSER=chrome <%= mobile %>
samsung_galaxy_s5: WEB_BROWSER=samsung_galaxy_s5 HOST_BROWSER=chrome <%= mobile %>
samsung_galaxy_s6: WEB_BROWSER=samsung_galaxy_s6 HOST_BROWSER=chrome <%= mobile %>
pixel: WEB_BROWSER=pixel HOST_BROWSER=chrome <%= mobile %>
pixel_xl: WEB_BROWSER=pixel_xl HOST_BROWSER=chrome <%= mobile %>
windows_phone7: WEB_BROWSER=windows_phone7 HOST_BROWSER=chrome <%= mobile %>
windows_phone8: WEB_BROWSER=windows_phone8 HOST_BROWSER=chrome <%= mobile %>
lumia_950_xl: WEB_BROWSER=lumia_950_xl HOST_BROWSER=chrome <%= mobile %>
blackberry_z10: WEB_BROWSER=blackberry_z10 HOST_BROWSER=chrome <%= mobile %>
blackberry_z30: WEB_BROWSER=blackberry_z30 HOST_BROWSER=chrome <%= mobile %>
blackberry_leap: WEB_BROWSER=blackberry_leap HOST_BROWSER=chrome <%= mobile %>
blackberry_passport: WEB_BROWSER=blackberry_passport HOST_BROWSER=chrome <%= mobile %>
#==============
# profiles for mobile device screen orientation
#==============
portrait: ORIENTATION=portrait
landscape: ORIENTATION=landscape
#==============
# profiles for mobile Safari web browsers hosted within XCode iOS simulator
# NOTE: Requires installation of XCode, iOS version specific target simulators, Appium, and the appium_capybara gem
#==============
appium_ios: WEB_BROWSER=appium AUTOMATION_ENGINE=XCUITest APP_PLATFORM_NAME="ios" APP_BROWSER="Safari" NEW_COMMAND_TIMEOUT=30 SHOW_SIM_KEYBOARD=false
app_ios_15: --profile appium_ios APP_VERSION="15.2"
ipad_pro_12_9_15_sim: --profile app_ios_15 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (12.9-inch) (5th generation)" <%= desktop %>
ipad_air_15_sim: --profile app_ios_15 DEVICE_TYPE=tablet APP_DEVICE="iPad Air (4th generation)" <%= desktop %>
#==============
# profiles for mobile Safari web browsers running on physically connected iOS devices
# NOTE: Requires installation of XCode, Appium, and the appium_capybara gem
#==============
my_ios_15_iphone: --profile app_ios_15 DEVICE_TYPE=phone APP_DEVICE="My Test iPhoneX" APP_UDID="INSERT YOUR DEVICE UDID"
my_ios_15_ipad: --profile app_ios_15 DEVICE_TYPE=tablet APP_DEVICE="My Test iPad Pro" APP_UDID="INSERT YOUR DEVICE UDID"
#==============
# profiles for Android mobile web browsers hosted within Android Studio Android Virtual Device emulators
# NOTE: Requires installation of Android Studio, Android version specific virtual device simulators, Appium, and the appium_capybara gem
#==============
appium_android: WEB_BROWSER=appium APP_PLATFORM_NAME="Android" <%= mobile %>
app_android_12: --profile appium_android APP_BROWSER="Chrome" APP_VERSION="12.0"
pixel_c_api31_sim: --profile app_android_12 DEVICE_TYPE=tablet APP_DEVICE="Pixel_C_API_31"
#==============
# profiles for remotely hosted web browsers on the BrowserStack service
#==============
browserstack: WEB_BROWSER=browserstack BS_USERNAME="<INSERT USER NAME HERE>" BS_AUTHKEY="<INSERT PASSWORD HERE>"
bs_desktop: --profile browserstack <%= desktop %> RESOLUTION="1920x1080"
bs_mobile: --profile browserstack <%= mobile %>
# BrowserStack macOS desktop browser profiles
bs_macos_monterey: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="Monterey"
bs_chrome_monterey: --profile bs_macos_monterey BS_BROWSER="Chrome" BS_VERSION="latest"
bs_edge_monterey: --profile bs_macos_monterey BS_BROWSER="Edge" BS_VERSION="latest"
bs_safari_monterey: --profile bs_macos_monterey BS_BROWSER="Safari" BS_VERSION="latest"
# BrowserStack Windows desktop browser profiles
bs_win11: --profile bs_desktop BS_OS="Windows" BS_OS_VERSION="11"
bs_chrome_win11: --profile bs_win11 BS_BROWSER="Chrome" BS_VERSION="latest"
bs_edge_win11: --profile bs_win11 BS_BROWSER="Edge" BS_VERSION="latest"
bs_win10: --profile bs_desktop BS_OS="Windows" BS_OS_VERSION="10"
bs_ie_win10: --profile bs_win10 BS_BROWSER="IE" BS_VERSION="11.0"
# BrowserStack iOS mobile browser profiles
bs_ipad: --profile bs_mobile BS_OS=ios BS_BROWSER=Safari DEVICE_TYPE=tablet BS_REAL_MOBILE="true"
bs_ipad_pro_12: --profile bs_ipad BS_DEVICE="iPad Pro 12.9 2018" BS_OS_VERSION="15"
# BrowserStack Android mobile browser profiles
bs_android: --profile bs_mobile BS_OS=android BS_BROWSER=Chrome DEVICE_TYPE=tablet BS_REAL_MOBILE="true"
bs_android_tablet: --profile bs_android BS_DEVICE="Samsung Galaxy Tab S7" BS_OS_VERSION="10.0"
#==============
# profiles for remotely hosted web browsers on the SauceLabs service
#==============
saucelabs: WEB_BROWSER=saucelabs SL_USERNAME="<INSERT USER NAME HERE>" SL_AUTHKEY="<INSERT PASSWORD HERE>" DATA_CENTER="<INSERT DATA CENTER HERE"
sl_desktop: --profile saucelabs <%= desktop %>
sl_mobile: --profile saucelabs <%= mobile %>
# SauceLabs macOS desktop browser profiles
sl_macos_monterey: --profile sl_desktop SL_OS="macOS 12" RESOLUTION="1920x1440"
sl_chrome_monterey: --profile sl_macos_monterey SL_BROWSER="chrome" SL_VERSION="latest"
sl_edge_monterey: --profile sl_macos_monterey SL_BROWSER="MicrosoftEdge" SL_VERSION="latest"
sl_firefox_monterey: --profile sl_macos_monterey SL_BROWSER="Firefox" SL_VERSION="latest"
# SauceLabs Windows desktop browser profiles
sl_windows: --profile sl_desktop RESOLUTION="1920x1200"
sl_edge_win11: --profile sl_windows SL_OS="Windows 11" SL_BROWSER="MicrosoftEdge" SL_VERSION="latest"
sl_ie_win10: --profile sl_windows SL_OS="Windows 10" SL_BROWSER="internet explorer" SL_VERSION="11"
# SauceLabs iOS mobile browser profiles
sl_ipad: --profile sl_mobile DEVICE_TYPE=tablet SL_PLATFORM=iOS SL_BROWSER=Safari
sl_ipad_pro_12: --profile sl_ipad SL_DEVICE="iPad Pro (12.9 inch) (5th generation) Simulator" SL_VERSION="15.0"
#==============
# profiles for remotely hosted web browsers on the TestingBot service
#==============
testingbot: WEB_BROWSER=testingbot TB_USERNAME="<INSERT USER NAME HERE>" TB_AUTHKEY="<INSERT PASSWORD HERE>"
tb_desktop: --profile testingbot <%= desktop %> RESOLUTION="1920x1200"
# TestingBot macOS desktop browser profiles
tb_macos_monterey: --profile tb_desktop TB_OS="MONTEREY"
tb_chrome_monterey: --profile tb_macos_monterey TB_BROWSER="chrome" TB_VERSION="latest"
tb_edge_monterey: --profile tb_macos_monterey TB_BROWSER="microsoftedge" TB_VERSION="latest"
# TestingBot Windows desktop browser profiles
tb_win11: --profile tb_desktop TB_OS="WIN11"
tb_edge_win11: --profile tb_win11 TB_BROWSER="microsoftedge" TB_VERSION="latest"
tb_win10: --profile tb_desktop TB_OS="WIN10"
tb_ie_win10: --profile tb_win10 TB_BROWSER="internet explorer" TB_VERSION="11"
#==============
# profiles for remotely hosted web browsers on the LambdaTest service
#==============
lambdatest: WEB_BROWSER=lambdatest LT_USERNAME=<INSERT USER NAME HERE> LT_AUTHKEY=<INSERT PASSWORD HERE>
lt_desktop: --profile lambdatest <%= desktop %> RESOLUTION="2560x1440"
# LambdaTest macOS desktop browser profiles
lt_macos_monterey: --profile lt_desktop LT_OS="MacOS Monterey"
lt_chrome_monterey: --profile lt_macos_monterey LT_BROWSER="Chrome" LT_VERSION="98.0"
lt_edge_monterey: --profile lt_macos_monterey LT_BROWSER="MicrosoftEdge" LT_VERSION="97.0"
# LambdaTest Windows desktop browser profiles
lt_win11: --profile lt_desktop LT_OS="Windows 11"
lt_edge_win11: --profile lt_win11 LT_BROWSER="MicrosoftEdge" LT_VERSION="98.0"
lt_win10: --profile lt_desktop LT_OS="Windows 10"
lt_i0_win11: --profile lt_win10 LT_BROWSER="Internet Explorer" LT_VERSION="11.0"
To specify a locally hosted target browser using a profile at runtime, you use the flag --profile
or -p
followed by the profile name when
invoking Cucumber in the command line. For instance, the following command invokes Cucumber and specifies that a local instance of Firefox
will be used as the target web browser:
$ cucumber -p firefox
The following command specifies that Cucumber will run tests against an instance of Chrome hosted within a Dockerized Selenium Grid environment"
$ cucumber -p chrome -p grid
The following command specifies that Cucumber will run tests against a local instance of Chrome, which will be used to emulate an iPad Pro in landscape orientation:
$ cucumber -p ipad_pro -p landscape
The following command specifies that Cucumber will run tests against an iPad Pro with iOS version 9.3 in an XCode Simulator in landscape orientation:
$ cucumber -p ipad_pro_93_sim -p landscape
NOTE: Appium must be running prior to executing this command
The following command specifies that Cucumber will run tests against a remotely hosted Safari web browser running on an OS X Mojave virtual machine on the BrowserStack service:
cucumber -p bs_safari_mojave
The following command specifies that Cucumber will run tests against a remotely hosted Mobile Safari web browser on an iPhone 6s Plus in landscape orientation running on the BrowserStack service:
$ cucumber -p bs_iphone6_plus -p landscape
Recommended Project Organization and Structure
Below is an example of the project structure of a typical Cucumber based test automation framework with a Page Object Model
architecture. PageObject
class definitions should be stored in the /features/support/pages
folder, organized in functional
area sub-folders as needed. Likewise, PageSection
class definitions should be stored in the /features/support/sections
folder.
my_automation_project
├── config
│ ├── locales
│ ├── test_data
│ └── cucumber.yml
├── downloads
├── features
│ ├── step_definitions
│ └── support
│ │ ├── pages
│ │ ├── sections
│ │ ├── env.rb
│ │ ├── hooks.rb
│ │ └── world_pages.rb
├── Gemfile
└── README.md
Web Test Automation Framework Implementation
Copyright and License
TestCentricity™ Framework is Copyright (c) 2014-2022, Tony Mrozinski. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.