insite 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4da6a0c60f82d3ad461cbdc4bbfc42e6e0208931036e163cc25449dd68bb9e75
-  data.tar.gz: e2c2d2e684de2dd576e33333e098e64a0f85bcd5640a49ab3baec85a12a53649
+  metadata.gz: 13879616cc34d431a33d53db3af85542fdb2cd7c66c368312a3215bb07074a3a
+  data.tar.gz: 79332f41805f595642a174cd78ab31c32d175718ce2c666f503d79853c1c847b
 SHA512:
-  metadata.gz: '081c49de90abf6786fb8ae7f9d0d060e9495d2031ef9689d3fbcfec806f410b8bde274568164a57760a946e39f61c4b305776c412826f2c235fa967de9db61f3'
-  data.tar.gz: 7d76291c5bab8c5854484ec0c0407b60da715d0d99dc04e12933567fcd4c3faf82dbc99d6f9789dc365c0ad97260933c6656bee9d8f986c3a9a386c85c410014
+  metadata.gz: 2df8d7dea14cf1659fbab02a46c777fd8a49777ac46c650e4f0aa9dc6f7574e3d97f5cebd227618f5d09742e217ebd20e32990d8dbe0de70c2c84ed97c0cb9fe
+  data.tar.gz: 9fd6e73087a17e58764a976d81895b52fa9747b6d864a2104dee29d858f1c7f9a06b9cc3e3d33f772248790888a0d464ffda9a71b5af66a51a94169aff8b3969

data/lib/insite/version.rb

@@ -1,3 +1,3 @@
 module Insite
-  VERSION = '0.1.2'
+  VERSION = '0.1.3'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: insite
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - John Fitisoff
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-09-05 00:00:00.000000000 Z
+date: 2018-09-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -165,10 +165,16 @@ dependencies:
       - !ruby/object:Gem::Version
         version: 3.7.0
 description: "Insite is a page object library that allows you to work with your website
-  in\nmuch the same way that a user does. It also provides a highly portable, \nobject
-  oriented approach to modeling recurring features in your application\n(e.g., cards,
-  calendars. search widgets.) Reusable components that you write\nfor UI testing are
-  fully compatible with standard DOM elements."
+  in\na more natural way. It does this by providing a wrapper class for all of your\npages.
+  This wrapper (called a site object) functions as a sort of browser for\nyour page
+  objects. Benefits of this approach include simplified navigation \nand better error
+  handling when things go wrong.\n\nInsite also provides a highly portable, object
+  oriented approach to modeling\nrecurring features in your web application (e.g.,
+  cards, calendars, search \nwidgets, etc.) Components that you write are essentially
+  DOM extensions:\nThey can be referenced from other components or any standard DOM
+  object.\nThis interoperability with the DOM makes your component features more\naccessible
+  when writing tests and almost completely eliminates the need to\nwrite code to wire
+  your components up to pages or to get them to work with\nother components."
 email: jfitisoff@yahoo.com
 executables: []
 extensions: []
@@ -233,9 +239,15 @@ rubyforge_project:
 rubygems_version: 2.7.6
 signing_key: 
 specification_version: 4
-summary: Insite is a page object library that allows you to work with your website
-  in much the same way that a user does. It also provides a highly portable,  object
-  oriented approach to modeling recurring features in your application (e.g., cards,
-  calendars. search widgets.) Reusable components that you write for UI testing are
-  fully compatible with standard DOM elements.
+summary: 'Insite is a page object library that allows you to work with your website
+  in a more natural way. It does this by providing a wrapper class for all of your
+  pages. This wrapper (called a site object) functions as a sort of browser for your
+  page objects. Benefits of this approach include simplified navigation  and better
+  error handling when things go wrong.  Insite also provides a highly portable, object
+  oriented approach to modeling recurring features in your web application (e.g.,
+  cards, calendars, search  widgets, etc.) Components that you write are essentially
+  DOM extensions: They can be referenced from other components or any standard DOM
+  object. This interoperability with the DOM makes your component features more accessible
+  when writing tests and almost completely eliminates the need to write code to wire
+  your components up to pages or to get them to work with other components.'
 test_files: []