json_expressions 0.8.1 → 0.8.2

data/CHANGELOG.md

@@ -1,16 +1,21 @@
+### v0.8.2 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.8.1...0.8.2)
+
+* Bugfix: require 'rspec/core' instead of 'rspec' (#12 by @pda)
+* Improved matcher output when using RSpec (#11 by @milkcocoa)
+* Bugfix: fixed a bug where reusing the same matcher sometimes causes false negatives (#10 by @kophyo)
+* Various documentation improvements
+* Various Rakefile improvements. The gem now builds correctly on Travis
+
 ### v0.8.1 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.8.0...0.8.1)
 
 * Fat finger: reverted a change in 0.8.0 which changed the default value of `assume_unordered_arrays` from true to false. Added tests to make sure this never happens again.
 
-### v0.8.0 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.7.3...0.8.0)
+### v0.8.0 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.7.2...0.8.0)
 
 * Added Test::Unit support.
 * Added MiniTest::Spec support.
 * BREAKING: Changed internal structure of MiniTest support code. This shouldn't affect you unless you have been manually requiring and including the MiniTest helpers yourself.
 * Use of `WILDCARD_MATCHER` (the constant) inside a `MiniTest::Unit::TestCase` is now discouraged. Instead, you are encouraged to use `wildcard_matcher` (the method) instead. README has been updated.
-
-### v0.7.3 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.7.2...0.7.3)
-
 * Removed WILDCARD_MATCHER#match and the corresponding test. Since support for Object#match has been removed in v0.7.0, this should no longer be necessary.
 
 ### v0.7.2 [view commit logs](https://github.com/chancancode/json_expressions/compare/0.7.1...0.7.2)

data/README.md

@@ -1,6 +1,8 @@
 JSON Expressions
 ================
 
+[![Build Status](https://travis-ci.org/chancancode/json_expressions.png?branch=master)](https://travis-ci.org/chancancode/json_expressions)
+
 ## Introduction
 
 Your API is a contract between your service and your developers. It is important for you to know exactly what your JSON API is returning to the developers in order to make sure you don't accidentally change things without updating the documentations and/or bumping the API version number. Perhaps some controller tests for your JSON endpoints would help:
@@ -227,7 +229,7 @@ but not
   integer: Fixnum,
   float:   Float,
   string:  String,
-  boolean: Boolean,
+  boolean: Boolean, # See http://stackoverflow.com/questions/3028243/check-if-ruby-object-is-a-boolean#answer-3028378
   array:   Array,
   object:  Hash,
   null:    NilClass,
@@ -385,9 +387,9 @@ JsonExpressions::Matcher.assume_strict_arrays = false
 JsonExpressions::Matcher.assume_strict_hashes = false
 ```
 
-## Support for `MiniTest::Spec` (and other testing frameworks)
+## Support for other test frameworks
 
-The `Matcher` class itself is written in a testing-framework-agnostic manner. This allows you to easily write custom helpers/matchers for your favorite testing framework. `MiniTest::Spec` is on my TODO list, but it is not a high priority for me personally, as I don't use it myself. If you need this now, write it yourself and submit a pull request - it's really easy, I promise (see `lib/json_expressions/minitest/unit/helpers.rb` for inspiration).
+The `Matcher` class itself is written in a framework-agnostic manner. This allows you to easily write custom helpers/matchers for your favorite testing framework. If you wrote an adapter for another test frameworks and you'd like to share yhat with the world, please open a Pull Request.
 
 ## Contributing
 

data/lib/json_expressions/matcher.rb

@@ -50,9 +50,7 @@ module JsonExpressions
       match_json('(JSON ROOT)', @json, other)
     end
 
-    def match(other)
-      self =~ other
-    end
+    alias_method :match, :=~
 
     def to_s
       @json.to_s
@@ -61,7 +59,7 @@ module JsonExpressions
     private
 
     def reset!
-      @last_errot = nil
+      @last_error = nil
       @captures   = {}
     end
 
@@ -206,4 +204,4 @@ module JsonExpressions
       end
     end
   end
-end
+end

data/lib/json_expressions/minitest.rb

@@ -3,10 +3,6 @@ require 'minitest/spec'
 require 'json_expressions'
 require 'json_expressions/minitest/assertions'
 
-# module MiniTest::Assertions
-#   include JsonExpressions::MiniTest::Assertions
-# end
-
 class MiniTest::Unit::TestCase
   WILDCARD_MATCHER = JsonExpressions::WILDCARD_MATCHER
 

data/lib/json_expressions/rspec.rb

@@ -1,4 +1,4 @@
-require 'rspec'
+require 'rspec/core'
 require 'json_expressions'
 require 'json_expressions/rspec/matchers'
 

data/lib/json_expressions/rspec/matchers/match_json_expression.rb

@@ -1,4 +1,5 @@
 require 'json'
+require 'rspec/core'
 
 module JsonExpressions
   module RSpec
@@ -24,6 +25,10 @@ module JsonExpressions
         def failure_message_for_should_not
           "expected #{@target.inspect} not to match JSON expression #{@expected.inspect}"
         end
+
+        def description
+          "should equal JSON expression #{@expected.inspect}"
+        end
       end
 
       def match_json_expression(expected)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: json_expressions
 version: !ruby/object:Gem::Version
-  version: 0.8.1
+  version: 0.8.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-08-24 00:00:00.000000000 Z
+date: 2013-02-07 00:00:00.000000000 Z
 dependencies: []
 description: JSON matchmaking for all your API testing needs.
 email:
@@ -51,7 +51,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: 1.3.6
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.24
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: JSON Expressions