capybara_error_intel 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +1 -1
  3. data/capybara_error_intel.gemspec +1 -1
  4. data/lib/capybara_error_intel/dsl.rb +1 -0
  5. data/lib/capybara_error_intel/version.rb +1 -1
  6. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: 7b277ca0a65c2accc4fe3d184b5a6316300f1f93
4
- data.tar.gz: 753725ace06c7903af7635fce2aa940fac326a6a
3
+ metadata.gz: 9745f2fd1ace38c3a31a8a1fcb88a35bec2a259a
4
+ data.tar.gz: 8ea2d0cd77502360b3312949ff974b3ee0d95e20
5
5
  SHA512:
6
- metadata.gz: 6039fab260fdd7597eb66a6a8730288b46f1d618d63d4f147fd17cf22fe40107d71cbce118ee965c8cd7454d051cbb585ec5410f0ab4b7981d727e2c303c5f46
7
- data.tar.gz: 591d92977f83615f0a503bc58811b9c45e7e85fbfbd6f13509beed75e772320ba6746776a499247234d18a828e30140a6835b36e9b91f522e1d9e86669d66138
6
+ metadata.gz: a30f339c00a4e239e8dd44654489f50b3bd213d4423ddaa862d797fb1f0cd721644c224c9a20f7c362b1991a1ac57c45a41058ec8bd00b8ed7333c2c94828a74
7
+ data.tar.gz: 5b19d463c95f8baaf09eb859a5bf19d4723456f4aabb80bf0c208135b3a49f72413ddcd042ed0505bf516693b49de88db3fe1c806251c467b1876f31f4526aff
data/README.md CHANGED
@@ -42,7 +42,7 @@ end
42
42
  methods:
43
43
 
44
44
  - `has_selector?`
45
- - `has_text?`
45
+ - `has_text?` (and `has_content?` alias)
46
46
  - `has_title?`
47
47
 
48
48
  It should be rather trivial to add more of them like `has_css` etc. I will try
data/capybara_error_intel.gemspec CHANGED
@@ -10,7 +10,7 @@ Gem::Specification.new do |spec|
10
10
  spec.email = ['jobs@doriankarter.com']
11
11
 
12
12
  spec.summary = %q{Provides Capybara's heuristic error messages for Page Objects}
13
- spec.description = %q{Capybara provides excellent error messages for it's
13
+ spec.description = %q{Capybara provides excellent error messages for its
14
14
  built in predicate methods: has_selector?, has_text?,
15
15
  and has_title? but when those are used from Page
16
16
  Objects while exposing predicate methods from the
data/lib/capybara_error_intel/dsl.rb CHANGED
@@ -9,6 +9,7 @@ module CapybaraErrorIntel
9
9
  matcher = Capybara::RSpecMatchers::HaveText.new(*args)
10
10
  match_or_error(matcher)
11
11
  end
12
+ alias_method :has_content?, :has_text?
12
13
 
13
14
  def has_title?(title, options = {})
14
15
  matcher = Capybara::RSpecMatchers::HaveTitle.new(title, options)
data/lib/capybara_error_intel/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module CapybaraErrorIntel
2
- VERSION = "0.1.0"
2
+ VERSION = "0.1.1"
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: capybara_error_intel
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
  - Dorian Karter
@@ -169,7 +169,7 @@ dependencies:
169
169
  - !ruby/object:Gem::Version
170
170
  version: '2'
171
171
  description: |-
172
- Capybara provides excellent error messages for it's
172
+ Capybara provides excellent error messages for its
173
173
  built in predicate methods: has_selector?, has_text?,
174
174
  and has_title? but when those are used from Page
175
175
  Objects while exposing predicate methods from the