testcentricity_web 0.5.7.1 → 0.5.7.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9569e27215cf9488a0b1ac757fc3849b50e860f8
-  data.tar.gz: 69d04c8ff6316100bd97a6fcd3c631a007232555
+  metadata.gz: 7faf72a16ef3d97239d41482e371fc058d9ef3a6
+  data.tar.gz: 4cd7057f471425de8b0133901edfd13c5938acce
 SHA512:
-  metadata.gz: 5b58009042ebe9fce1f9376ca46730a5b27574ca0d41ff5050d24a638c3576cd76c47a31518cc12dba11decdd2e98a1817c0b6e48090c47d2ac832077a7fda25
-  data.tar.gz: 5dce0ce7e4600fc7dbc044ef9a267c1e2b790f5e0747aaace568658d4730e77d08d139abc6be1687c0ae05a91b02911af65281abc62ee3cd0d31ad24e583b4db
+  metadata.gz: a8fe539726416a107f76946c4eb0a42000bda0de53628d7737a0cebdb1a96c403b4f07767478cb237bc8cfcf95ba9f65a6c8309c071ddc9621494b8e2b41dd1a
+  data.tar.gz: 86b41962f01be7144ebc390ff5f5eb23bdef1f176a19b6c9ca5f1807b760f93e8830b9e9e18568aa46f95544ca3ffd7bbc9f0074b0ee3aab80e5d2d0e5937290

data/README.md

@@ -64,7 +64,7 @@ text field attributes, button captions, etc.), maintenance is performed in the *
 to update the affected feature file, scenarios, or step definitions.
 
 
-#### - Defining a Page Object
+#### 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:
@@ -83,7 +83,7 @@ test automation project. You define new **Page Objects** as shown below:
     end
 
 
-#### - Adding UI Elements to your Page Object
+#### Adding UI Elements to your Page Object
 
 **UI Elements** are added to your **Page Object** class definition as shown below:
 
@@ -108,7 +108,7 @@ below:
     login_page.login_button.click
 
 
-#### - Adding Methods to your Page Object
+#### 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
@@ -154,7 +154,7 @@ or a menu. **UI Elements** and functional behavior are confined to the scope of
 A **PageSection Object** may contain other **PageSection Objects**.
 
 
-#### - Defining a PageSection Object
+#### 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:
@@ -164,7 +164,7 @@ your test automation project. You define new **PageSection Objects** as shown be
     end
 
 
-#### - Adding UI Elements to your PageSection Object
+#### Adding UI Elements to your PageSection Object
 
 **UI Elements** are added to your **PageSection** class definition as shown below:
 
@@ -177,7 +177,7 @@ your test automation project. You define new **PageSection Objects** as shown be
     end
 
 
-#### - Adding Methods to your PageSection Object
+#### Adding Methods to your PageSection Object
 
 You can add high level methods to your **PageSection** class definition, as shown below:
 
@@ -195,7 +195,7 @@ You can add high level methods to your **PageSection** class definition, as show
     end
 
 
-#### - Adding PageSection Objects to your Page Object
+#### Adding PageSection Objects to your Page Object
 
 You add a **PageSection Object** to its associated **Page Object** as shown below:
 
@@ -244,7 +244,7 @@ The **WorldPages** module above can be defined in your *env.rb* file, or you can
 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
+#### 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** instance variables and their associated **Page Object** classes
@@ -289,7 +289,7 @@ Variables**are used to specify the target local or remote web browser, and the v
 the connection.
 
 
-#### - Locally hosted desktop web browser
+#### Locally hosted desktop web browser
 
 For locally hosted desktop web browsers, the **WEB_BROWSER** Environment Variable must be set to one of the values from the table below: 
 
@@ -299,11 +299,11 @@ firefox | OS X or Windows
 chrome | OS X or Windows
 safari | OS X only
 ie | Windows only
-edge | Windows only
+edge | Windows 10 only
 poltergeist | OS X or Windows
 
 
-#### - Locally hosted emulated mobile web browser
+#### Locally hosted emulated mobile web browser
 
 You can also run your tests against emulated mobile device browsers within a locally hosted instance of the Firefox desktop browser. You may
 even specify the emulated device's screen orientation. For locally hosted emulated mobile web browsers, the **WEB_BROWSER** Environment Variable
@@ -321,15 +321,118 @@ iphone6_plus |
 android_phone |
 android_tablet |
 
-To specify the emulated device's screen orientation, you set the **ORIENTATION** Environment Variable to either *portrait* or *landscape*.
+To specify the emulated device's screen orientation, you set the **ORIENTATION** Environment Variable to either ***portrait*** or ***landscape***.
 
 
-#### - Remotely hosted desktop web browser
+#### Remotely hosted desktop and mobile web browsers
 
-TBD
+You can run your automated tests against remotely hosted desktop and mobile web browsers using the BrowserStack, CrossBrowserTesting, or
+Sauce Labs services.
 
 
-#### - Using Browser specific Profiles in cucumber.yml
+##### 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](https://www.browserstack.com/automate/capabilities#capabilities-browserstack) 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 | Refer to ***browser_version*** capability in chart
+BS_LOCAL | Must be ***true*** if you are testing against internal/local servers
+RESOLUTION | Refer to supported screen ***resolution*** capability in chart
+
+
+##### 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](https://www.browserstack.com/automate/capabilities#capabilities-browserstack) 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_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_LOCAL | Must be ***true*** if you are testing against internal/local servers
+ORIENTATION | set to ***portrait*** or ***landscape***
+
+
+
+##### 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](https://app.crossbrowsertesting.com/selenium/run) 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 | Refer to supported ***screen_resolution*** capability in the sample script of the Wizard
+
+
+##### 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](https://app.crossbrowsertesting.com/selenium/run) 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
+
+
+
+##### 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](https://wiki.saucelabs.com/display/DOCS/Platform+Configurator#/) 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 | Refer to supported ***screenResolution*** capability in the Copy Code section of the Platform Configurator page
+
+
+##### Remote mobile browsers on the Sauce Labs service
+
+For remotely hosted mobile 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](https://wiki.saucelabs.com/display/DOCS/Platform+Configurator#/) 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_PLATFORM | Refer to ***platform*** capability in the Copy Code section of the Platform Configurator page
+SL_BROWSER | Must be set to ***iPhone*** or ***android***
+SL_VERSION | Refer to ***version*** capability in the Copy Code section of the Platform Configurator page
+SL_DEVICE | Refer to ***deviceName*** capability in the Copy Code section of the Platform Configurator page
+SL_DEVICE_TYPE | If displayed, refer to ***deviceType*** capability in the Copy Code section of the Platform Configurator page
+ORIENTATION | Refer to ***deviceOrientation*** capability in the Copy Code section of the Platform Configurator page
+
+
+
+#### 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
@@ -557,8 +660,22 @@ web browsers is to create browser specific **Profiles** that set the appropriate
     sl_android:         --profile sl_mobile SL_PLATFORM=Linux SL_BROWSER="android" SL_VERSION="4.4"
     sl_android_phone:   --profile sl_android SL_DEVICE="Android Emulator" SL_DEVICE_TYPE="phone"
     sl_android_tablet:  --profile sl_android SL_DEVICE="Android Emulator" SL_DEVICE_TYPE="tablet"
+
+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 Chrome
+will be used as the target web browser:
+    
+    cucumber -p chrome
     
+The following command specifies that Cucumber will run tests against a local instance of Firefox, 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 a remotely hosted Safari web browser running on an OS X Yosemite
+virtual machine on the BrowserStack service:
 
+    cucumber -p bs_safari_yos
 
 
 

data/lib/testcentricity_web/version.rb

@@ -1,3 +1,3 @@
 module TestCentricityWeb
-  VERSION = '0.5.7.1'
+  VERSION = '0.5.7.2'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: testcentricity_web
 version: !ruby/object:Gem::Version
-  version: 0.5.7.1
+  version: 0.5.7.2
 platform: ruby
 authors:
 - A.J. Mrozinski
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-03-20 00:00:00.000000000 Z
+date: 2016-03-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler