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 3.x).
An example project that demonstrates the implementation of a page object model framework using Cucumber and TestCentricity™ can be found here.
The TestCentricity™ Web gem supports running automated tests against the following web test targets:
- locally hosted desktop browsers (Firefox, Chrome, 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 or Firefox browsers
- desktop and emulated mobile web browsers hosted on Selenium Grid and Dockerized Selenium Grid 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
- enterprise web portals built using Siebel Open UI
- 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.
Installation
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
Page Objects
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 Page Object class definition only, typically with no need to update the affected feature file, scenarios, or step definitions.
Defining a Page Object
Your Page Object class definitions should be contained within individual .rb files in the features/support/pages folder of your
test automation project. You define new Page Objects as shown below:
class LoginPage < TestCentricity::PageObject
end
class HomePage < TestCentricity::PageObject
end
class RegistrationPage < TestCentricity::PageObject
end
Adding Traits to your Page Object
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 of the Page Objects 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 Page Object
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 Page Object 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 Page Object
It is good practice for your Cucumber step definitions to call high level methods in your your Page Object instead of directly accessing and interacting with a page object's UI elements. You can add high level methods to your Page Object 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 },
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
}
populate_data_fields(fields)
.click
end
end
Once your Page Objects have been instantiated, you can call your methods as shown below:
login_page.remember_me(true)
login_page.login('snicklefritz', 'Pa55w0rd')
PageSection Objects
A PageSection Object 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 Object may contain other PageSection Objects.
Defining a PageSection Object
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 Objects as shown below:
class SearchForm < TestCentricity::PageSection
end
Adding Traits to a PageSection Object
A PageSection Object typically has a root node object that encapsulates a collection of UI Elements. The section_locator trait
specifies the CSS or Xpath expression that uniquely identifies that root node object.
You define your page 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 Object
Page sections 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 Object
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 PageSection Objects to your Page Object
You add a PageSection Object to its associated Page Object 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 Page Object has been instantiated, you can call its PageSection methods as shown below:
home_page.search_form.search_for('ocarina')
UI Elements
Page Objects and PageSection Objects are typically made up of UI Element like text fields, check boxes, combo boxes, radio buttons, tables, lists, buttons, images, HTML5 video objects, HTML5 audio objects, etc. UI Elements are declared and instantiated within the class definition of the Page Object or PageSection Object in which they are contained. With TestCentricity Web, all UI elements are based on the UIElement class.
Declaring and Instantiating UI Element
Single UIElement declarations have the following format:
elementType :element Name, locator
- The
element nameis the unique name that you will use to refer to the UI element and is specified as a symbol. - The
locatoris the CSS or XPath attribute that uniquely and unambiguously identifies the UI element.
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 UI Element Declarations
Supported UI Element 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 UI Elements. 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.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?
Instantiating your Page Objects
Before you can call the methods in your Page Objects and PageSection Objects, you must instantiate the Page Objects of your web application, as well as create instance variables which can be used when calling a Page Objects methods from your step definitions. There are several ways to instantiate your Page Objects.
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 Page Objects), it quickly becomes cumbersome to manage if your web application has dozens of Page Objects that need to be instantiated and managed.
Using the PageManager
The PageManager class provides methods for supporting the instantiation and management of Page Objects. In the code example below,
the page_objects method contains a hash table of your Page Object instances and their associated Page Object 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 Page Objects 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 Page Objects 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)
case page_name
when 'Registration'
page = registration_page
when 'My Account'
page = my_account_page
when 'Terms & Conditions'
page = terms_conditions_page
when 'Privacy Policy'
page = privacy_policy_page
when 'Contact Us'
page = contact_us_page
when 'FAQs'
page = 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 Page Objects), it quickly becomes cumbersome to manage if your web application has dozens of Page Objects 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 version 55 or greater only) |
firefox_headless |
OS X or Windows (headless - no visible UI) |
safari |
OS X only |
ie |
Windows only (IE version 10.x or greater only) |
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 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
│ ├── step_definitions
│ ├── support
│ └── test_data
├── 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 paralle threads is depicted below:
my_automation_project
├── config
├── downloads
│ ├── 1
│ ├── 2
│ ├── 3
│ └── 4
├── features
│ ├── step_definitions
│ ├── support
│ └── test_data
├── 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 |
android_tablet |
chrome |
1024 x 768 | landscape | Android 3.0 |
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 |
android_phone |
chrome |
360 x 640 | portrait | Android 4.2.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.
Selenium Grid and Dockerized Selenium Grid hosted desktop and emulated mobile web browsers
For desktop and emulated mobile web browsers running on Selenium Grid or Dockerized Selenium Grid environments (like Zalenium), the following Environment Variables must be set as described in the table below.
| Environment Variable | Description |
|---|---|
WEB_BROWSER |
Must be set to one of the following desktop browsers - chrome, chrome_headless, firefox, ie, edge, or safari 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 |
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 12.2, 11.4, 10.3.1, 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 6s Plus, iPad Pro (10.5-inch), iPad Air 2, 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 |
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 |
Remotely hosted desktop and mobile web browsers
You can run your automated tests against remotely hosted desktop and mobile web browsers using the BrowserStack, CrossBrowserTesting,
Sauce Labs, TestingBot, Gridlastic, 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.
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 |
BROWSER_SIZE |
[Optional] Specify width, height of browser window |
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. |
SELENIUM_VERSION |
[Optional] Specify Selenium WebDriver version to use |
CONSOLE_LOGS |
[Optional] Used to capture browser console logs. Refer to browserstack.console capability in chart |
WD_VERSION |
[Optional] Specify browser-specific WebDriver version to use. Refer to browserstack.geckodriver, browserstack.ie.driver, and browserstack.safari.driver capabilities in chart |
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 |
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 iPhone, iPad, or android |
BS_PLATFORM |
Must be set to MAC (for iOS) or 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. |
CONSOLE_LOGS |
[Optional] Used to capture browser console logs. Refer to browserstack.console capability in chart |
Remote desktop browsers on the CrossBrowserTesting service
For remotely hosted desktop web browsers on the CrossBrowserTesting service, the following Environment Variables must be set as described in the table below. Use the Configuration Wizard on the Start a Selenium Test page to obtain information regarding the specific capabilities.
| Environment Variable | Description |
|---|---|
WEB_BROWSER |
Must be set to crossbrowser |
CB_USERNAME |
Must be set to your CrossBrowserTesting account user name or email address |
CB_AUTHKEY |
Must be set to your CrossBrowserTesting account access key |
CB_OS |
Refer to os_api_name capability in the sample script of the Wizard |
CB_BROWSER |
Refer to browser_api_name capability in the sample script of the Wizard |
RESOLUTION |
[Optional] Refer to supported screen_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) |
Remote mobile browsers on the CrossBrowserTesting service
For remotely hosted mobile web browsers on the CrossBrowserTesting service, the following Environment Variables must be set as described in the table below. Use the Configuration Wizard on the Start a Selenium Test page to obtain information regarding the specific capabilities.
| Environment Variable | Description |
|---|---|
WEB_BROWSER |
Must be set to crossbrowser |
CB_USERNAME |
Must be set to your CrossBrowserTesting account user name or email address |
CB_AUTHKEY |
Must be set to your CrossBrowserTesting account access key |
CB_PLATFORM |
Refer to os_api_name capability in the sample script of the Wizard |
CB_BROWSER |
Refer to browser_api_name capability in the sample script of the Wizard |
RESOLUTION |
Refer to supported screen_resolution capability in the sample script of the Wizard |
DEVICE_TYPE |
Must be set to phone or tablet |
RECORD_VIDEO |
[Optional] Enable screen video recording during test execution (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 |
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 mobile browsers on the TestingBot service
For remotely hosted mobile 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 |
Must be set to MAC (for iOS) or ANDROID |
TB_BROWSER |
Must be set to safari (for iOS) or browser (for Android) |
TB_VERSION |
Refer to version capability in chart |
TB_PLATFORM |
Must be set to iOS or ANDROID |
TB_DEVICE |
Refer to deviceName capability in chart |
DEVICE_TYPE |
Must be set to phone or tablet |
TUNNELING |
Must be true if you are testing against internal/local servers (true or false) |
ORIENTATION |
[Optional] Set to portrait or landscape |
Remote desktop browsers on the Gridlastic service
For remotely hosted desktop web browsers on the Gridlastic service, the following Environment Variables must be set as described in the table below. Refer to the Gridlastic Selenium Grid Test Environments for information regarding the specific capabilities.
| Environment Variable | Description |
|---|---|
WEB_BROWSER |
Must be set to gridlastic |
GL_USERNAME |
Must be set to your Gridlastic account user name |
GL_AUTHKEY |
Must be set to your Gridlastic account access key |
GL_SUBDOMAIN |
Must be set to your Gridlastic subdomain |
GL_OS |
Refer to platform capability in chart |
GL_BROWSER |
Refer to browserName capability in chart |
GL_VERSION |
Refer to version capability in chart |
GL_PLATFORM |
Must be set to windows when running on Windows operating systems |
RECORD_VIDEO |
[Optional] Enable screen video recording during test execution (true or false) |
VIDEO_URL |
[Optional] Video Files Location Endpoint URL shown in the Your Selenium Grid Credentials section of the Gridlastic Dashboard |
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, CrossBrowserTesting, Sauce Labs, TestingBot, Gridlastic 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. When using the Gridlastic service, you will also need replace the INSERT SUBDOMAIN HERE
placeholder text with the Subdomain specified on the Grid Configuration Parameters section of the Gridlastic Dashboard.
<% 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 %>
safari: WEB_BROWSER=safari <%= desktop %>
ie: WEB_BROWSER=ie <%= desktop %>
chrome_headless: WEB_BROWSER=chrome_headless <%= desktop %>
firefox_headless: WEB_BROWSER=firefox_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 %>
android_phone: WEB_BROWSER=android_phone HOST_BROWSER=chrome <%= mobile %>
nexus6: WEB_BROWSER=nexus6 HOST_BROWSER=chrome <%= mobile %>
android_tablet: WEB_BROWSER=android_tablet HOST_BROWSER=chrome <%= tablet %>
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 APP_PLATFORM_NAME="iOS" APP_BROWSER="Safari" <%= mobile %>
app_ios_10: --profile appium_ios APP_VERSION="10.3"
app_ios_11: --profile appium_ios APP_VERSION="11.2"
iphone_7_plus_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone 7 Plus"
iphone_7_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone 7"
iphone_7se_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone SE"
iphone_6s_plus_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone 6s Plus"
iphone_6s_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone 6s"
iphone_SE_10_sim: --profile app_ios_10 DEVICE_TYPE=phone APP_DEVICE="iPhone SE"
iphone_X_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone X"
iphone_8_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 8"
iphone_8_plus_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 8 Plus"
iphone_7_plus_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 7 Plus"
iphone_7_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 7"
iphone_7se_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone SE"
iphone_6s_plus_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 6s Plus"
iphone_6s_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone 6s"
iphone_SE_11_sim: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="iPhone SE"
ipad_pro_12_9_11_sim: --profile app_ios_11 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (12.9-inch)"
ipad_pro_12_9_10_sim: --profile app_ios_10 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (12.9-inch)"
ipad_pro_10_5_11_sim: --profile app_ios_11 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (10.5-inch)"
ipad_pro_10_5_10_sim: --profile app_ios_10 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (10.5-inch)"
ipad_pro_9_7_11_sim: --profile app_ios_11 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (9.7-inch)"
ipad_pro_9_7_10_sim: --profile app_ios_10 DEVICE_TYPE=tablet APP_DEVICE="iPad Pro (9.7-inch)"
ipad_air_2_11_sim: --profile app_ios_11 DEVICE_TYPE=tablet APP_DEVICE="iPad Air 2"
ipad_air_2_10_sim: --profile app_ios_10 DEVICE_TYPE=tablet APP_DEVICE="iPad Air 2"
#==============
# 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_11_3_iphone: --profile app_ios_11 DEVICE_TYPE=phone APP_DEVICE="My Test iPhoneX" APP_UDID="INSERT YOUR DEVICE UDID"
my_ios_10_3_ipad: --profile app_ios_10 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 %>
android_api_26: --profile appium_android APP_BROWSER="Chrome" APP_VERSION="8.0"
android_api_23: --profile appium_android APP_BROWSER="Browser" APP_VERSION="6.0"
pixel_xl_api26_sim: --profile android_api_26 DEVICE_TYPE=phone APP_DEVICE="Pixel_XL_API_26"
pixel_2_xl_api26_sim: --profile android_api_26 DEVICE_TYPE=phone APP_DEVICE="Pixel_2_XL_API_26"
nexus_6_api23_sim: --profile android_api_23 DEVICE_TYPE=phone APP_DEVICE="Nexus_6_API_23"
#==============
# 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 OS X desktop browser profiles
bs_macos_mojave: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="Mojave"
bs_ff_mojave: --profile bs_macos_mojave BS_BROWSER="Firefox"
bs_chrome_mojave: --profile bs_macos_mojave BS_BROWSER="Chrome"
bs_safari_mojave: --profile bs_macos_mojave BS_BROWSER="Safari"
bs_macos_high_sierra: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="High Sierra"
bs_ff_high_sierra: --profile bs_macos_high_sierra BS_BROWSER="Firefox"
bs_chrome_high_sierra: --profile bs_macos_high_sierra BS_BROWSER="Chrome"
bs_safari_high_sierra: --profile bs_macos_high_sierra BS_BROWSER="Safari"
bs_macos_sierra: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="Sierra"
bs_ff_sierra: --profile bs_macos_sierra BS_BROWSER="Firefox"
bs_chrome_sierra: --profile bs_macos_sierra BS_BROWSER="Chrome"
bs_safari_sierra: --profile bs_macos_sierra BS_BROWSER="Safari"
bs_osx_el_capitan: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="El Capitan"
bs_ff_el_cap: --profile bs_osx_el_capitan BS_BROWSER="Firefox"
bs_chrome_el_cap: --profile bs_osx_el_capitan BS_BROWSER="Chrome"
bs_safari_el_cap: --profile bs_osx_el_capitan BS_BROWSER="Safari"
bs_osx_yosemite: --profile bs_desktop BS_OS="OS X" BS_OS_VERSION="Yosemite"
bs_ff_yos: --profile bs_osx_yosemite BS_BROWSER="Firefox"
bs_chrome_yos: --profile bs_osx_yosemite BS_BROWSER="Chrome"
bs_safari_yos: --profile bs_osx_yosemite BS_BROWSER="Safari"
# BrowserStack Windows desktop browser profiles
bs_win8: --profile bs_desktop BS_OS="Windows" BS_OS_VERSION="8"
bs_win10: --profile bs_desktop BS_OS="Windows" BS_OS_VERSION="10"
bs_ff_win8: --profile bs_win8 BS_BROWSER="Firefox"
bs_ff_win10: --profile bs_win10 BS_BROWSER="Firefox"
bs_chrome_win8: --profile bs_win8 BS_BROWSER="Chrome"
bs_chrome_win10: --profile bs_win10 BS_BROWSER="Chrome"
bs_ie10_win8: --profile bs_win8 BS_BROWSER="IE" BS_VERSION="10.0"
bs_ie11_win8: --profile bs_desktop BS_OS="Windows" BS_OS_VERSION="8.1" BS_BROWSER="IE" BS_VERSION="11.0"
bs_ie11_win10: --profile bs_win10 BS_BROWSER="IE" BS_VERSION="11.0"
bs_edge_win10: --profile bs_win10 BS_BROWSER="Edge" BS_VERSION="15.0"
# BrowserStack iOS mobile browser profiles
bs_iphone: --profile bs_mobile BS_PLATFORM=MAC BS_OS=ios BS_BROWSER=iPhone DEVICE_TYPE=phone
bs_iphone6s_plus: --profile bs_iphone BS_DEVICE="iPhone 6S Plus"
bs_iphone6s: --profile bs_iphone BS_DEVICE="iPhone 6S"
bs_iphone6_plus: --profile bs_iphone BS_DEVICE="iPhone 6 Plus"
bs_iphone6: --profile bs_iphone BS_DEVICE="iPhone 6"
bs_iphone5s: --profile bs_iphone BS_DEVICE="iPhone 5S"
bs_iphone4s: --profile bs_iphone BS_DEVICE="iPhone 4S (6.0)"
bs_ipad: --profile bs_mobile BS_PLATFORM=MAC BS_BROWSER=iPad DEVICE_TYPE=tablet
bs_ipad_pro: --profile bs_ipad BS_DEVICE="iPad Pro"
bs_ipad_air2: --profile bs_ipad BS_DEVICE="iPad Air 2"
bs_ipad_air: --profile bs_ipad BS_DEVICE="iPad Air"
bs_ipad_mini: --profile bs_ipad BS_DEVICE="iPad Mini 4"
# BrowserStack iOS real device mobile browser profiles
bs_iphone_device: --profile bs_iphone BS_REAL_MOBILE="true"
bs_iphoneX: --profile bs_iphone_device BS_OS_VERSION="11.0" BS_DEVICE="iPhone X"
bs_iphone8_plus: --profile bs_iphone_device BS_OS_VERSION="11.0" BS_DEVICE="iPhone 8 Plus"
bs_iphone8: --profile bs_iphone_device BS_OS_VERSION="11.0" BS_DEVICE="iPhone 8"
bs_iphone7_plus: --profile bs_iphone_device BS_OS_VERSION="10.3" BS_DEVICE="iPhone 7 Plus"
bs_iphone7: --profile bs_iphone_device BS_OS_VERSION="10.3" BS_DEVICE="iPhone 7"
bs_ipad_device: --profile bs_ipad BS_REAL_MOBILE="true"
bs_ipad5: --profile bs_ipad_device BS_OS_VERSION="11.0" BS_DEVICE="iPad 5th"
# BrowserStack Android mobile browser profiles
bs_android: --profile bs_mobile BS_PLATFORM=ANDROID BS_BROWSER=android BS_OS=android
bs_android_phone: --profile bs_android DEVICE_TYPE=phone
bs_galaxy_s5: --profile bs_android_phone BS_DEVICE="Samsung Galaxy S5"
bs_nexus5: --profile bs_android_phone BS_DEVICE="Google Nexus 5"
bs_moto_razr: --profile bs_android_phone BS_DEVICE="Motorola Razr"
bs_sony_xperia: --profile bs_android_phone BS_DEVICE="Sony Xperia Tipo"
bs_android_tablet: --profile bs_android DEVICE_TYPE=tablet
bs_kindle_fire_hd89: --profile bs_android_tablet BS_DEVICE="Amazon Kindle Fire HD 8.9"
bs_kindle_fire_hdx7: --profile bs_android_tablet BS_DEVICE="Amazon Kindle Fire HDX 7"
bs_kindle_fire2: --profile bs_android_tablet BS_DEVICE="Amazon Kindle Fire 2"
bs_nexus7: --profile bs_android_tablet BS_DEVICE="Google Nexus 7"
# BrowserStack Android real device mobile browser profiles
bs_android_device: --profile bs_mobile BS_BROWSER=android BS_OS=android BS_REAL_MOBILE="true"
bs_google_pixel8: --profile bs_android_device BS_DEVICE="Google Pixel" BS_OS_VERSION="8.0" DEVICE_TYPE=phone
bs_google_pixel71: --profile bs_android_device BS_DEVICE="Google Pixel" BS_OS_VERSION="7.1" DEVICE_TYPE=phone
bs_nexus6: --profile bs_android_device BS_DEVICE="Google Nexus 6" DEVICE_TYPE=phone
bs_galaxy_s8_plus: --profile bs_android_device BS_DEVICE="Samsung Galaxy S8 Plus" DEVICE_TYPE=phone
bs_galaxy_s8: --profile bs_android_device BS_DEVICE="Samsung Galaxy S8" DEVICE_TYPE=phone
bs_galaxy_s7: --profile bs_android_device BS_DEVICE="Samsung Galaxy S7" DEVICE_TYPE=phone
bs_galaxy_s6: --profile bs_android_device BS_DEVICE="Samsung Galaxy S6" DEVICE_TYPE=phone
bs_galaxy_note4: --profile bs_android_device BS_DEVICE="Samsung Galaxy Note 4" DEVICE_TYPE=tablet
bs_nexus9: --profile bs_android_device BS_DEVICE="Google Nexus 9" DEVICE_TYPE=tablet
#==============
# profiles for remotely hosted web browsers on the CrossBrowserTesting service
#==============
crossbrowser: WEB_BROWSER=crossbrowser CB_USERNAME="<INSERT USER NAME HERE>" CB_AUTHKEY="<INSERT PASSWORD HERE>"
cb_desktop: --profile crossbrowser <%= desktop %>
cb_mobile: --profile crossbrowser <%= mobile %>
# CrossBrowserTesting OS X desktop browser profiles
cb_osx: --profile cb_desktop RESOLUTION="1920x1200"
cb_macos_sierra: --profile cb_osx CB_OS="Mac10.12"
cb_chrome_sierra: --profile cb_macos_sierra CB_BROWSER="Chrome53x64"
cb_safari_sierra: --profile cb_macos_sierra CB_BROWSER="Safari10"
cb_osx_el_capitan: --profile cb_osx CB_OS="Mac10.11"
cb_ff_el_cap: --profile cb_osx_el_capitan CB_BROWSER="FF46"
cb_chrome_el_cap: --profile cb_osx_el_capitan CB_BROWSER="Chrome48x64"
cb_safari_el_cap: --profile cb_osx_el_capitan CB_BROWSER="Safari9"
cb_osx_yosemite: --profile cb_osx CB_OS="Mac10.10"
cb_ff_yos: --profile cb_osx_yosemite CB_BROWSER="FF46"
cb_chrome_yos: --profile cb_osx_yosemite CB_BROWSER="Chrome48x64"
cb_safari_yos: --profile cb_osx_yosemite CB_BROWSER="Safari8"
# CrossBrowserTesting Windows desktop browser profiles
cb_win: --profile cb_desktop RESOLUTION="1920x1080"
cb_win8: --profile cb_win CB_OS="Win8"
cb_win10: --profile cb_win CB_OS="Win10"
cb_ff_win8: --profile cb_win8 CB_BROWSER="FF46"
cb_ff_win10: --profile cb_win10 CB_BROWSER="FF46"
cb_chrome_win8: --profile cb_win8 CB_BROWSER="Chrome48x64"
cb_chrome_win10: --profile cb_win10 CB_BROWSER="Chrome48x64"
cb_edge_win10: --profile cb_win10 CB_BROWSER="Edge20"
cb_ie11_win8: --profile cb_win8 CB_BROWSER="IE11"
cb_ie10_win8: --profile cb_win8 CB_BROWSER="IE10"
cb_ie11_win10: --profile cb_win10 CB_BROWSER="IE11"
# CrossBrowserTesting iOS mobile browser profiles
cb_iphone6s_plus: --profile cb_mobile DEVICE_TYPE=phone CB_PLATFORM="iPhone6sPlus-iOS9sim" CB_BROWSER="MblSafari9.0" RESOLUTION="1242x2208"
cb_iphone6s: --profile cb_mobile DEVICE_TYPE=phone CB_PLATFORM="iPhone6s-iOS9sim" CB_BROWSER="MblSafari9.0" RESOLUTION="750x1334"
cb_iphone6_plus: --profile cb_mobile DEVICE_TYPE=phone CB_PLATFORM="iPhone6Plus-iOS8sim" CB_BROWSER="MblSafari8.0" RESOLUTION="1242x2208"
cb_iphone6: --profile cb_mobile DEVICE_TYPE=phone CB_PLATFORM="iPhone6-iOS8sim" CB_BROWSER="MblSafari8.0" RESOLUTION="750x1334"
cb_iphone5s: --profile cb_mobile DEVICE_TYPE=phone CB_PLATFORM="iPhone5s-iOS7sim" CB_BROWSER="MblSafari7.0" RESOLUTION="640x1136"
cb_ipad_pro: --profile cb_mobile DEVICE_TYPE=tablet CB_PLATFORM="iPadPro-iOS9Sim" CB_BROWSER="MblSafari9.0" RESOLUTION="2732x2048"
cb_ipad_air2: --profile cb_mobile DEVICE_TYPE=tablet CB_PLATFORM="iPadAir2-iOS9Sim" CB_BROWSER="MblSafari9.0" RESOLUTION="2048x1536"
cb_ipad_air: --profile cb_mobile DEVICE_TYPE=tablet CB_PLATFORM="iPadAir-iOS8Sim" CB_BROWSER="MblSafari8.0" RESOLUTION="2048x1536"
cb_ipad_mini: --profile cb_mobile DEVICE_TYPE=tablet CB_PLATFORM="iPadMiniRetina-iOS7Sim" CB_BROWSER="MblSafari7.0" RESOLUTION="2048x1536"
# CrossBrowserTesting Android mobile browser profiles
cb_nexus7: --profile cb_mobile CB_PLATFORM="Nexus7-And42" CB_BROWSER="MblChrome37" RESOLUTION="800x1280"
cb_galaxy_tab2: --profile cb_mobile CB_PLATFORM="GalaxyTab2-And41" CB_BROWSER="MblChrome38" RESOLUTION="1280x800"
cb_galaxy_s5: --profile cb_mobile CB_PLATFORM="GalaxyS5-And44" CB_BROWSER="MblChrome35" RESOLUTION="1080x1920"
cb_galaxy_s4: --profile cb_mobile CB_PLATFORM="GalaxyS4-And42" CB_BROWSER="MblChrome33" RESOLUTION="1080x1920"
#==============
# 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>"
sl_desktop: --profile saucelabs <%= desktop %>
# SauceLabs OS X desktop browser profiles
sl_osx_sierra: --profile sl_desktop SL_OS="macOS 10.12"
sl_ff_sierra: --profile sl_osx_sierra SL_BROWSER="firefox"
sl_chrome_sierra: --profile sl_osx_sierra SL_BROWSER="chrome"
sl_safari_sierra: --profile sl_osx_sierra SL_BROWSER="safari"
sl_osx_el_capitan: --profile sl_desktop SL_OS="OS X 10.11"
sl_ff_el_cap: --profile sl_osx_el_capitan SL_BROWSER="firefox"
sl_chrome_el_cap: --profile sl_osx_el_capitan SL_BROWSER="chrome"
sl_safari_el_cap: --profile sl_osx_el_capitan SL_BROWSER="safari"
sl_osx_yosemite: --profile sl_desktop SL_OS="OS X 10.10" RESOLUTION="1920x1200"
sl_ff_yos: --profile sl_osx_yosemite SL_BROWSER="firefox"
sl_chrome_yos: --profile sl_osx_yosemite SL_BROWSER="chrome"
sl_safari_yos: --profile sl_osx_yosemite SL_BROWSER="safari"
# SauceLabs Windows desktop browser profiles
sl_win8: --profile sl_desktop SL_OS="Windows 8.1" RESOLUTION="1280x1024"
sl_win10: --profile sl_desktop SL_OS="Windows 10" RESOLUTION="1280x1024"
sl_ff_win8: --profile sl_win8 SL_BROWSER="firefox"
sl_ff_win10: --profile sl_win10 SL_BROWSER="firefox"
sl_chrome_win8: --profile sl_win8 SL_BROWSER="chrome"
sl_chrome_win10: --profile sl_win10 SL_BROWSER="chrome"
sl_ie11_win8: --profile sl_win8 SL_BROWSER="internet explorer" SL_VERSION="11.0"
sl_ie11_win10: --profile sl_win10 SL_BROWSER="internet explorer"
#==============
# 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"
tb_mobile: --profile testingbot <%= mobile %>
# TestingBot OS X desktop browser profiles
tb_macos_sierra: --profile tb_desktop TB_OS="SIERRA"
tb_ff_sierra: --profile tb_macos_sierra TB_BROWSER="firefox"
tb_chrome_sierra: --profile tb_macos_sierra TB_BROWSER="chrome"
tb_safari_sierra: --profile tb_macos_sierra TB_BROWSER="safari" TB_VERSION="10"
tb_osx_el_capitan: --profile tb_desktop TB_OS="CAPITAN"
tb_ff_el_cap: --profile tb_osx_el_capitan TB_BROWSER="firefox"
tb_chrome_el_cap: --profile tb_osx_el_capitan TB_BROWSER="chrome"
tb_safari_el_cap: --profile tb_osx_el_capitan TB_BROWSER="safari" TB_VERSION="9"
tb_osx_yosemite: --profile tb_desktop TB_OS="YOSEMITE"
tb_ff_yos: --profile tb_osx_yosemite TB_BROWSER="firefox"
tb_chrome_yos: --profile tb_osx_yosemite TB_BROWSER="chrome"
tb_safari_yos: --profile tb_osx_yosemite TB_BROWSER="safari" TB_VERSION="8"
# TestingBot Windows desktop browser profiles
tb_win8: --profile tb_desktop TB_OS="WIN8"
tb_win10: --profile tb_desktop TB_OS="WIN10"
tb_ff_win8: --profile tb_win8 TB_BROWSER="firefox"
tb_ff_win10: --profile tb_win10 TB_BROWSER="firefox"
tb_chrome_win8: --profile tb_win8 TB_BROWSER="chrome"
tb_chrome_win10: --profile tb_win10 TB_BROWSER="chrome"
tb_ie11_win8: --profile tb_win8 TB_BROWSER="internet explorer" TB_VERSION="11"
tb_ie10_win8: --profile tb_win8 TB_BROWSER="internet explorer" TB_VERSION="10"
tb_ie11_win10: --profile tb_win10 TB_BROWSER="internet explorer" TB_VERSION="11"
tb_edge_win10: --profile tb_win10 TB_BROWSER="microsoftedge" TB_VERSION="14"
# TestingBot iOS mobile browser profiles
tb_ios: --profile tb_mobile TB_OS="MAC" TB_BROWSER="safari" TB_PLATFORM="iOS"
tb_iphone6s_plus_10: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="10.0" TB_DEVICE="iPhone 6s Plus"
tb_iphone6s_plus_93: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="9.3" TB_DEVICE="iPhone 6s Plus"
tb_iphone6_plus_10: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="10.0" TB_DEVICE="iPhone 6 Plus"
tb_iphone6_plus_93: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="9.3" TB_DEVICE="iPhone 6 Plus"
tb_iphone6s_10: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="10.0" TB_DEVICE="iPhone 6s"
tb_iphone6s_93: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="9.3" TB_DEVICE="iPhone 6s"
tb_iphone5s_10: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="10.0" TB_DEVICE="iPhone 5s"
tb_iphone5s_93: --profile tb_ios DEVICE_TYPE=phone TB_VERSION="9.3" TB_DEVICE="iPhone 5s"
tb_ipad_pro_10: --profile tb_ios DEVICE_TYPE=tablet TB_VERSION="10.0" TB_DEVICE="iPad Pro"
tb_ipad_pro_93: --profile tb_ios DEVICE_TYPE=tablet TB_VERSION="9.3" TB_DEVICE="iPad Pro"
tb_ipad_air2_10: --profile tb_ios DEVICE_TYPE=tablet TB_VERSION="10.0" TB_DEVICE="iPad Air 2"
tb_ipad_air2_93: --profile tb_ios DEVICE_TYPE=tablet TB_VERSION="9.3" TB_DEVICE="iPad Air 2"
# TestingBot Android mobile browser profiles
tb_android: --profile tb_mobile TB_OS="ANDROID" TB_BROWSER="browser" TB_PLATFORM="Android"
tb_nexus_s: --profile tb_android TB_VERSION="6.0" TB_DEVICE="Nexus S"
tb_nexus_1: --profile tb_android TB_VERSION="5.0" TB_DEVICE="Nexus 1"
tb_nexus_4: --profile tb_android TB_VERSION="6.0" TB_DEVICE="Nexus 4"
tb_galaxy_nexus: --profile tb_android TB_VERSION="4.4" TB_DEVICE="Galaxy Nexus"
tb_galaxy_s4: --profile tb_android TB_VERSION="4.4" TB_DEVICE="Galaxy S4"
tb_galaxy_s5: --profile tb_android TB_VERSION="5.0" TB_DEVICE="Galaxy S5"
tb_galaxy_s6: --profile tb_android TB_VERSION="6.0" TB_DEVICE="Galaxy S6"
#==============
# profiles for remotely hosted web browsers on the Gridlastic service
#==============
gridlastic: WEB_BROWSER=gridlastic GL_USERNAME="<INSERT USER NAME HERE>" GL_AUTHKEY="<INSERT PASSWORD HERE>" GL_SUBDOMAIN="<INSERT SUBDOMAIN HERE>"
gl_video: RECORD_VIDEO="True" VIDEO_URL="<INSERT VIDEO URL HERE>"
gl_desktop: --profile gridlastic --profile gl_video <%= desktop %>
# Gridlastic Windows desktop browser profiles
gl_windows: --profile gl_desktop GL_PLATFORM="windows"
gl_win8: --profile gl_windows GL_OS="WIN8"
gl_win8_1: --profile gl_windows GL_OS="WIN8_1"
gl_win10: --profile gl_windows GL_OS="WIN10"
gl_ff_win8: --profile gl_win8_1 GL_BROWSER="firefox" GL_VERSION="59"
gl_ff_win10: --profile gl_win10 GL_BROWSER="firefox" GL_VERSION="59"
gl_chrome_win8: --profile gl_win8_1 GL_BROWSER="chrome" GL_VERSION="latest"
gl_chrome_win10: --profile gl_win10 GL_BROWSER="chrome" GL_VERSION="latest"
gl_ie11_win8: --profile gl_win8_1 GL_BROWSER="internet explorer" GL_VERSION="11"
gl_ie10_win8: --profile gl_win8 GL_BROWSER="internet explorer" GL_VERSION="10"
gl_ie11_win10: --profile gl_win10 GL_BROWSER="internet explorer" GL_VERSION="11"
# Gridlastic Linux desktop browser profiles
gl_chrome_linux: --profile gl_desktop GL_OS="LINUX" GL_BROWSER="chrome" GL_VERSION="latest"
#==============
# 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="1920x1080"
lt_firefox: LT_BROWSER="Firefox" LT_VERSION="67.0"
lt_chrome: LT_BROWSER="Chrome" LT_VERSION="76.0"
lt_safari: LT_BROWSER="Safari" ALLOW_COOKIES="true" ALLOW_POPUPS="true"
# LambdaTest OS X desktop browser profiles
lt_macos_mojave: --profile lt_desktop LT_OS="macOS Mojave"
lt_ff_mojave: --profile lt_macos_mojave --profile lt_firefox
lt_chrome_mojave: --profile lt_macos_mojave --profile lt_chrome
lt_safari_mojave: --profile lt_macos_mojave --profile lt_safari LT_VERSION="12.0"
lt_macos_high_sierra: --profile lt_desktop LT_OS="macOS High Sierra"
lt_ff_high_sierra: --profile lt_macos_high_sierra --profile lt_firefox
lt_chrome_high_sierra: --profile lt_macos_high_sierra --profile lt_chrome
lt_safari_high_sierra: --profile lt_macos_high_sierra --profile lt_safari LT_VERSION="11.0"
lt_macos_sierra: --profile lt_desktop LT_OS="macOS Sierra"
lt_ff_sierra: --profile lt_macos_sierra --profile lt_firefox
lt_chrome_sierra: --profile lt_macos_sierra --profile lt_chrome
lt_safari_sierra: --profile lt_macos_sierra --profile lt_safari LT_VERSION="10.0"
# LambdaTest Windows desktop browser profiles
lt_win10: --profile lt_desktop LT_OS="Windows 10"
lt_ff_win10: --profile lt_win10 --profile lt_firefox
lt_chrome_win10: --profile lt_win10 --profile lt_chrome
lt_ie11_win10: --profile lt_win10 LT_BROWSER="Internet Explorer" LT_VERSION="11.0"
lt_edge_win10: --profile lt_win10 LT_BROWSER="MicrosoftEdge" LT_VERSION="18.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
Web Test Automation Framework Implementation
Copyright and License
TestCentricity™ Framework is Copyright (c) 2014-2020, 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.