capybara_error_intel 0.1.2 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f5e604de308508f4a6b425d6563b0b5dfcbd54d0
-  data.tar.gz: e3af7516188351093fc5c62b08dbbed26a571e27
+  metadata.gz: 5862341b63629cf16f8b3339b62789c905b61170
+  data.tar.gz: b9472f2a9161625dbea7f8596fa49dc074ba8108
 SHA512:
-  metadata.gz: a4c816bc8b6767b5e67ac0632959aee5b8a7b85057b773f726cd2ce40b381856de108bbc2d9a06c4d8846ffcb6e4a22dc657c528e8ee6a22f56c8927a4f85516
-  data.tar.gz: 5f6b128f2f80ddcdcc4956e1cf83f1b805b59458c2a954133c9852b336d767534aee64b35babbf9451c9659e3cce7c8e5566a7bb1e4025104ade511e88910b93
+  metadata.gz: 33d204d510b83490e5fff56da2b4018c79fb6f031ff8eedfe6195ec60b995b5a6672f6009a480df95d3497e063795fbe66e2fdfffd0cdc66f7e2a87597f833e8
+  data.tar.gz: 332f5782bf6eac411f4b6a01ff76159d8e97e0b89ef930809053113a5728a6b8c6a4170bb15a573658c2eb5f6f450b2cfc1a6796f51778a8ce6d5a8eb4aeb715

data/README.md

@@ -63,9 +63,18 @@ end
   Note: currently this gem only supports the following Capybara built-in predicate
   methods:
 
-  - `has_selector?`
-  - `has_text?` (and `has_content?` alias)
-  - `has_title?`
+  - `has_selector?(*args)`
+  - `has_text?(*args)` (and `has_content?` alias)
+  - `has_title?(title, options={})`
+  - `has_css?(css, options={})`
+  - `has_button?(locator, options={})`
+  - `has_field?(locator, options={})`
+  - `has_xpath?(xpath, options={})`
+  - `has_checked_field?(locator, options={})`
+  - `has_unchecked_field?(locator, options={})`
+  - `has_select?(locator, options={})`
+  - `has_table?(locator, options={})`
+
 
   It should be rather trivial to add more of them like `has_css` etc. I will try
   to implement the rest in the near future but feel free to submit a pull

data/capybara_error_intel.gemspec

@@ -12,7 +12,7 @@ Gem::Specification.new do |spec|
   spec.summary       = %q{Provides Capybara's heuristic error messages for Page Objects}
   spec.description   = %q{Capybara provides excellent error messages for its
                           built in predicate methods: has_selector?, has_text?,
-                          and has_title? but when those are used from Page
+                          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".

data/lib/capybara_error_intel/dsl.rb

@@ -1,33 +1,79 @@
 module CapybaraErrorIntel
   module DSL
     def has_selector?(*args)
-      matcher = Capybara::RSpecMatchers::HaveSelector.new(*args)
+      matcher = has_selector(*args)
       match_or_error(matcher)
     end
 
+    def has_css?(css, options={})
+      has_selector?(:css, css, options)
+    end
+
+    def has_button?(locator, options={})
+      has_selector?(:button, locator, options)
+    end
+
+    def has_field?(locator, options={})
+      has_selector?(:field, locator, options)
+    end
+
+    def has_xpath?(xpath, options={})
+      has_selector?(:xpath, locator, options)
+    end
+
+    def has_checked_field?(locator, options={})
+      has_selector?(:field, locator, options.merge(:checked => true))
+    end
+
+    def has_unchecked_field?(locator, options={})
+      has_selector?(:field, locator, options.merge(:unchecked => true))
+    end
+
+    def has_select?(locator, options={})
+      has_selector?(:select, locator, options)
+    end
+
+    def has_table?(locator, options={})
+      has_selector?(:table, locator, options)
+    end
+
     def has_text?(*args)
-      matcher = Capybara::RSpecMatchers::HaveText.new(*args)
+      matcher = has_text(*args)
       match_or_error(matcher)
     end
     alias_method :has_content?, :has_text?
 
     def has_title?(title, options = {})
-      matcher = Capybara::RSpecMatchers::HaveTitle.new(title, options)
+      matcher = has_title(title, options)
       match_or_error(matcher)
     end
 
-    def match_or_error(matcher)
-      matcher.matches?(Capybara.current_session) || handle_failure(matcher)
-    end
+    private
 
-    def handle_failure(matcher)
-      message = matcher.failure_message
+      def has_selector(*args)
+        Capybara::RSpecMatchers::HaveSelector.new(*args)
+      end
 
-      if matcher.respond_to?(:diffable?) && matcher.diffable?
-        RSpec::Expectations.fail_with message, matcher.expected, matcher.actual
-      else
-        RSpec::Expectations.fail_with message
+      def has_text(*args)
+        Capybara::RSpecMatchers::HaveText.new(*args)
+      end
+
+      def has_title(title, options)
+        Capybara::RSpecMatchers::HaveTitle.new(title, options)
+      end
+
+      def match_or_error(matcher)
+        matcher.matches?(Capybara.current_session) || handle_failure(matcher)
+      end
+
+      def handle_failure(matcher)
+        message = matcher.failure_message
+
+        if matcher.respond_to?(:diffable?) && matcher.diffable?
+          RSpec::Expectations.fail_with message, matcher.expected, matcher.actual
+        else
+          RSpec::Expectations.fail_with message
+        end
       end
-    end
   end
 end

data/lib/capybara_error_intel/version.rb

@@ -1,3 +1,3 @@
 module CapybaraErrorIntel
-  VERSION = "0.1.2"
+  VERSION = "1.0.0"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capybara_error_intel
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 1.0.0
 platform: ruby
 authors:
 - Dorian Karter
@@ -171,7 +171,7 @@ dependencies:
 description: |-
   Capybara provides excellent error messages for its
                             built in predicate methods: has_selector?, has_text?,
-                            and has_title? but when those are used from Page
+                            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".