insite 0.1.0 → 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/lib/insite/version.rb +1 -1
  3. metadata +11 -11
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: ff0c306e9463fd4190878e92ddf560df01c426c617019c36be931948e24b65e2
4
- data.tar.gz: 3ff42e536b0e3e324ff73c8bed4788f17075cbec8684c43acb892bf2ee33339a
3
+ metadata.gz: 6e5c3c3292766218a4fdd6580526a7f6c34ee53a60e61477fe63599562e52507
4
+ data.tar.gz: 76ef07457e86b531f3e43d2aa8f26ffd17a5ddcc38ba1ec26924d4306f00beec
5
5
  SHA512:
6
- metadata.gz: fd5cc232ca61766e2e137ec0457e953fb56f23f772bcc9273fb2641436a3acdfe279e75f471efbc093aa33a3dc6a54ae87a8a24834834923040a93f27784ddc4
7
- data.tar.gz: 84facfc95ccf63e0c9b260ed6644ca8cbffd91cb569adc6573b38985589cbd6011220481465941bad178ca2e6a9faae7ada668ff0993e972470123aaa6bab476
6
+ metadata.gz: 76da84bd7b04272db6c83e34f285f532c4547cd016a4522c0666d1d5d6c2a2775c6a6d4d343c2aad4124eee73177dbede5825f6c83b704f8e199eb20f651274d
7
+ data.tar.gz: '08ead004638cfac8ed2639cccaa967ce8042709a52d1f7b2db7fbde069ef2a85fa2c78f749a6b3b4ec3061b0ed12baca48c98ce586c1ff40f2a44124a5a79b7e'
@@ -1,3 +1,3 @@
1
1
  module Insite
2
- VERSION = '0.1.0'
2
+ VERSION = '0.1.1'
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: insite
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.0
4
+ version: 0.1.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - John Fitisoff
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-08-23 00:00:00.000000000 Z
11
+ date: 2018-09-05 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: activesupport
@@ -164,7 +164,10 @@ dependencies:
164
164
  - - ">="
165
165
  - !ruby/object:Gem::Version
166
166
  version: 3.7.0
167
- description: Page object library with support for component-based web frameworks
167
+ description: |
168
+ Insite is a page object library that allows you to work with your website in much the same way as an actual user does. It provides a page object browser (called a site object) for your page objects. Site objects are smart: They can determine which page they on and whether or not a page object has been defined for the currently displayed page. Benefits are simplified navigation, better error handling when things go wrong and less code needed to maintain your site and write tests.
169
+
170
+ Insite also provides a highly flexible, object-oriented approach to writing code for reusable features. It supports this via _components_, which can be thought of as DOM extensions. Components are fully interoperable with standard DOM elements and other components. When a component is defined, you get accessor methods for each page that belongs to your site, one for an individual instance of the component and another
168
171
  email: jfitisoff@yahoo.com
169
172
  executables: []
170
173
  extensions: []
@@ -229,12 +232,9 @@ rubyforge_project:
229
232
  rubygems_version: 2.7.6
230
233
  signing_key:
231
234
  specification_version: 4
232
- summary: Insite is a page object library that's geared towards writing reusable code
233
- for component-based web applications. It allows you to write reusable test components
234
- that model your application components. These components are interchangable with
235
- regular DOM objects. Insite uses a "Site Object Model." You create a site object
236
- class and define pages and components for the site. You then use the site object
237
- as the interface to your application instead of declaring individual pages each
238
- time that the site context changes. Think of the site object as a browser for page
239
- objects.
235
+ summary: Insite is a page object library that allows you to work with your website
236
+ in much the same way as an actual user does. This library also provides a highly
237
+ portable, object oriented approach to modeling recurring features in your application
238
+ (e,g, cards, calendars. search widgets.) Reusable components that you write for
239
+ UI testing are fully compatible with standard DOM elements.
240
240
  test_files: []