capybara_error_intel 1.0.2 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: ebab2dc2cf570ed1a3c8a6e578cd2eaa309f21f5
-  data.tar.gz: 5732238ef77ad3b3a90c9a5386425549fc8b2ac2
+SHA256:
+  metadata.gz: 7dd3ed928524f6ff13429a6e96f7981d05c2d158c0f6ab5e87e5af8aac66c6a4
+  data.tar.gz: 3a9a9653e48ba39119e434b03d020393b040b92be15b5e0b6a553ecc729074ea
 SHA512:
-  metadata.gz: e0b827c5919d385a41de269a980ac11b5f2f331751ceb26cf179f2d672648221c462f9482cbb9b9a699d280c30f1b760779fdd6c4397c2d945c63bfcfa772d95
-  data.tar.gz: 5c10884e7d213d895b2c4573e35812502ae5c2014fe9108e869d7ba5a50c987963aa17d731b1fa3dfeeb09a2fca52915f78e2a020d5831810ac753c64c9e1d79
+  metadata.gz: 3a5733d4daa7833b7af20c2a2083d83e060bbad7b85f73aaebcfb188284ba354ff417ed79bf097c6fe0093b988c3f68350f10655cf7fd6923d9d45378c44f75b
+  data.tar.gz: 47d4470bbe114454303886da0e06aced64537dc3507eb92c875cd6b0823a9da16025de8fad507ace662e0d19b1661e4831370df087972e9b2e8a85c273745e66

data/.rubocop.yml

@@ -6,4 +6,6 @@ AllCops:
   Exclude:
     - '*.gemspec'
     - 'vendor/**/*'
-
+Metrics/BlockLength:
+  Exclude:
+    - 'spec/**/**'

data/CHANGELOG.md

@@ -0,0 +1,3 @@
+# v1.1.0
+
+- Allow Capybara 3.x, update spec for proper error text (thanks @geoffharcourt)

data/README.md

@@ -1,6 +1,6 @@
 ![CapybaraErrorIntel](img/CapybaraErrorIntel.png)
 
-[![Build Status](https://travis-ci.org/dkarter/capybara_error_intel.svg?branch=master)](https://travis-ci.org/dkarter/capybara_error_intel) [![Code Climate](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/gpa.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel) [![Test Coverage](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/coverage.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel/coverage) [![Issue Count](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/issue_count.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel)
+[![Build Status](https://travis-ci.org/dkarter/capybara_error_intel.svg?branch=master)](https://travis-ci.org/dkarter/capybara_error_intel) [![CircleCI](https://circleci.com/gh/dkarter/capybara_error_intel.svg?style=svg)](https://circleci.com/gh/dkarter/capybara_error_intel) [![Code Climate](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/gpa.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel) [![Test Coverage](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/coverage.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel/coverage) [![Issue Count](https://codeclimate.com/github/dkarter/capybara_error_intel/badges/issue_count.svg)](https://codeclimate.com/github/dkarter/capybara_error_intel) [![Gem Version](https://badge.fury.io/rb/capybara_error_intel.svg)](https://badge.fury.io/rb/capybara_error_intel) ![downloads counter](http://ruby-gem-downloads-badge.herokuapp.com/capybara_error_intel)
 
 Capybara provides excellent error messages for its built in predicate methods: `has_selector?`, `has_text?`, `has_title?` etc., but when those are used from Page Objects while exposing predicate methods from the PageObjects themselves the error messages are lost and all we get is `expected true, got false`.  Including this module into your PageObject by adding `include CapybaraErrorIntel::DSL` after `include Capybara::DSL` will return the heuristic error messages.
 
@@ -79,6 +79,38 @@ end
   It should be rather trivial to add more of them. Please open an issue or submit a pull request if something you need is missing.
 
 
+### Accessing original predicate methods from your Page Object
+
+If you ever need to access the overwritten Capybara predicate methods you can do
+so by using Capybara's `page` for example:
+
+
+```ruby
+module Pages
+  class PostIndex
+    include Capybara::DSL
+    include CapybaraErrorIntel::DSL
+
+    def has_header?(header_text)
+      page.has_selector?('h1', text: header_text)
+    end
+  end
+end
+
+```
+
+This will allow you to have negative assertions. That being said I strongly
+discourage the use of negative assertions, especially with waiting Capybara
+methods such as `has_selector?` since they can make your test suite really slow.
+
+```ruby
+expect(post_index_page).to_not have_header('POSTS')
+```
+
+> Note: I'm considering changing CapybaraErrorIntel for v2 to expose the
+> predicate methods as bang methods, both positive and negative e.g.
+> `has_selector!` and `has_no_selector!`. Please share your thoughts in the
+> issues section.
 
 ## Development
 

data/Rakefile

@@ -5,4 +5,4 @@ require 'rubocop/rake_task'
 RuboCop::RakeTask.new
 RSpec::Core::RakeTask.new(:spec)
 
-task default: [:spec, :rubocop]
+task default: %i[spec rubocop]

data/capybara_error_intel.gemspec

@@ -32,13 +32,13 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'launchy', '~> 0'
   spec.add_development_dependency 'rack', '~> 1.6', '>= 1.6.4'
   spec.add_development_dependency 'rack-test', '~> 0.5', '>= 0.5.4'
+  spec.add_development_dependency 'codeclimate-test-reporter', '~> 1.0.0'
   spec.add_development_dependency 'pry'
   spec.add_development_dependency 'pry-byebug'
   spec.add_development_dependency 'rubocop'
   spec.add_development_dependency 'cadre'
   spec.add_development_dependency 'simplecov'
-  spec.add_development_dependency 'codeclimate-test-reporter'
 
   spec.add_runtime_dependency 'rspec', '>= 2.1', '< 4.x'
-  spec.add_runtime_dependency 'capybara', '~> 2'
+  spec.add_runtime_dependency 'capybara', '>= 2.0', '< 4.x'
 end

data/lib/capybara_error_intel/version.rb

@@ -1,3 +1,3 @@
 module CapybaraErrorIntel
-  VERSION = '1.0.2'.freeze
+  VERSION = '1.1.0'.freeze
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: capybara_error_intel
 version: !ruby/object:Gem::Version
-  version: 1.0.2
+  version: 1.1.0
 platform: ruby
 authors:
 - Dorian Karter
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-10-28 00:00:00.000000000 Z
+date: 2018-05-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -113,21 +113,21 @@ dependencies:
       - !ruby/object:Gem::Version
         version: 0.5.4
 - !ruby/object:Gem::Dependency
-  name: pry
+  name: codeclimate-test-reporter
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 1.0.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 1.0.0
 - !ruby/object:Gem::Dependency
-  name: pry-byebug
+  name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -141,7 +141,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: rubocop
+  name: pry-byebug
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -155,7 +155,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: cadre
+  name: rubocop
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -169,7 +169,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: simplecov
+  name: cadre
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -183,7 +183,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: codeclimate-test-reporter
+  name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -220,16 +220,22 @@ dependencies:
   name: capybara
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '2.0'
+    - - "<"
       - !ruby/object:Gem::Version
-        version: '2'
+        version: 4.x
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '2'
+        version: '2.0'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: 4.x
 description: |-
   Capybara provides excellent error messages for its
                             built in predicate methods: has_selector?, has_text?,
@@ -252,6 +258,7 @@ files:
 - ".rspec"
 - ".rubocop.yml"
 - ".travis.yml"
+- CHANGELOG.md
 - Gemfile
 - LICENSE.txt
 - README.md
@@ -285,7 +292,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.5.1
+rubygems_version: 2.7.3
 signing_key: 
 specification_version: 4
 summary: Provides Capybara's heuristic error messages for Page Objects