gridium 0.2.2 → 0.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: fa53796b32752f73131f570064f809f00b36a88e
-  data.tar.gz: 34520a57779e259536f90e1e3b24ada51300d910
+  metadata.gz: c5b97b15990a724513d715ccb5e84c83078bee0b
+  data.tar.gz: e49dc32244857906d0f321a04d254eacc96887d4
 SHA512:
-  metadata.gz: 4930494ce2ef104a66f3d7db02ec1c4fe71c7af813a8c9302a9b4c421a9e48209bc07755b9950f26147a901625739446d357dd3835d810b573980e86942894ad
-  data.tar.gz: e2a3a6dcc023cfb15a0492696f33af1b5a02be824c4e1eba2b7e19fee54c86e24d18fd387deccfbde5317f463d6f6443cbb1a7162c7a48e3e4ab14481f301e5e
+  metadata.gz: 23e6df5a7e7e18bf49181af7fcde59a19420c1d75bc96f29b3bff1847c70745d8d9f56fa4b13b3cdeecd0caf69d901f3de37cb3fecc859c0c05c5c03f38f8f38
+  data.tar.gz: fdfc5ad5f910a07a4395707db65d4f165fef6667f660894098595869c0d99638f828bd4bd11b1b870fc426587583f3c030ed3d6bc684c3680be9fb48887abdbb

data/README.md

@@ -146,7 +146,33 @@ $errors_total = 0
 Spec_data.load_suite_state
 Spec_data.load_spec_state
 ```
+##Saving screenshots to S3
 
+S3 support is available for persisting screenshots online. This is especially helpful when running tests in CI and/or Docker environments.
+
+#### 1. Setup environment variables
+```
+export S3_ACCESS_KEY_ID="your access key"
+export S3_SECRET_ACCESS_KEY="your secret access key"
+export S3_DEFAULT_REGION="your region"
+export S3_ROOT_BUCKET="your root bucket"
+```
+#### 2. Setup spec_helper file
+
+```
+  #inside Gridium.configure do |config|
+  config.screenshots_to_s3 = true
+  config.project_name_for_s3 = 'name the folder below the root bucket'
+  config.subdirectory_name_for_s3 = 'name for folder just below that, probably dynamic to mitigate ginormous directories'
+
+```
+
+#### 3. Integrate into a test
+```
+Driver.visit('https://the-internet.herokuapp.com/')
+driver.save_screenshot()
+#based on your needs, choose how to publish this screenshot to your interested parties
+```
 ## Page Objects
 
 Page objects are required for Gridium.  Page objects abstract the functionality of the page away from the test.  There's a million reasons why page objects are the way to go.  Not the least of all is that it helps you maintain your tests.

data/lib/element.rb

@@ -151,6 +151,17 @@ class Element
     end
   end
 
+  # Raw webdriver mouse over
+  def mouse_over
+    Log.debug("Triggering mouse over for (#{self.to_s})...")
+    if element.enabled?
+      $verification_passes += 1
+      ElementExtensions.mouse_over(self)
+    else
+      Log.error('Cannot mouse over.  Element is not present.')
+    end
+  end
+
   def scroll_into_view
     if element.enabled?
       $verification_passes += 1
@@ -160,6 +171,16 @@ class Element
     end
   end
 
+  def trigger_onblur
+    Log.debug("Triggering onblur for (#{self.to_s})...")
+    if element.enabled?
+      $verification_passes += 1
+      ElementExtensions.trigger_onblur(self)
+    else
+      Log.error('Cannot trigger onblur.  Element is not present.')
+    end
+  end
+
   def size
     element.size
   end

data/lib/element_extensions.rb

@@ -27,4 +27,12 @@ class Gridium::ElementExtensions
     Driver.execute_script("var evObj = document.createEvent('MouseEvents'); evObj.initMouseEvent(\"mouseout\",true, false, window, 0, 0, 0, 0, 0, false, false, false, false, 0, null); arguments[0].dispatchEvent(evObj);", element.element)
     sleep 1
   end
-end
+
+  def self.mouse_over(element)
+    Driver.driver.mouse.move_to(element.element)
+  end
+
+  def self.trigger_onblur(element)
+    Driver.execute_script("arguments[0].focus(); arguments[0].blur(); return true", element.element)
+  end
+end

data/lib/gridium/version.rb

@@ -1,3 +1,3 @@
 module Gridium
-  VERSION = "0.2.2"
+  VERSION = "0.2.3"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: gridium
 version: !ruby/object:Gem::Version
-  version: 0.2.2
+  version: 0.2.3
 platform: ruby
 authors:
 - Seth Urban
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2016-12-14 00:00:00.000000000 Z
+date: 2016-12-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler