Changelog for ruby2.7-rubygem-rspec-expectations-3_5-3.5.0-lp153.3.17.x86_64.rpm :

* Thu Nov 16 2017 opensuse_buildserviceAATTojkastl.de- created versioned gem for version 3.5
* Tue Jun 13 2017 cooloAATTsuse.com- updated to version 2.14.5 see installed Changelog.md [#]## 2.14.5 / 2014-02-01 [full changelog](http://github.com/rspec/rspec-expectations/compare/v2.14.4...v2.14.5) Bug fixes
* Fix wrong matcher descriptions with falsey expected value (yujinakayama)
* Mon May 29 2017 opensuse_buildserviceAATTojkastl.de- changed package name with suffix -2_14, renamed spec and changes file
* Tue May 23 2017 opensuse_buildserviceAATTojkastl.de- changed naming of the package, as this is a versioned gem
* Tue Jul 15 2014 mrueckertAATTsuse.com- regenerate with new template
* Thu Jun 26 2014 mrueckertAATTsuse.com- move to SLE 12 packaging schema
* Fri Nov 22 2013 cooloAATTsuse.com- updated to version 2.14.4 [full changelog](http://github.com/rspec/rspec-expectations/compare/v2.14.3...v2.14.4) Bug fixes
* Make the `match` matcher produce a diff output. (Jon Rowe, Ben Moss)
* Choose encoding for diff\'s more intelligently, and when all else fails fall back to default internal encoding with replacing characters. (Jon Rowe)
* Fri Oct 04 2013 cooloAATTsuse.com- updated to version 2.14.3 Bug fixes
* Fix operator matchers (`should` syntax) when `method` is redefined on target. (Brandon Turner)
* Fix diffing of hashes with object based keys. (Jon Rowe)
* Fix operator matchers (`should` syntax) when operator is defined via `method_missing` (Jon Rowe)
* Mon Aug 26 2013 cooloAATTsuse.com- updated to version 2.14.2 Bug fixes
* Fix `be_` matcher to not support operator chaining like the `be` matcher does (e.g. `be == 5`). This led to some odd behaviors since `be_ == anything` returned a `BeComparedTo` matcher and was thus always truthy. This was a consequence of the implementation (e.g. subclassing the basic `Be` matcher) and was not intended behavior. (Myron Marston).
* Fix `change` matcher to compare using `==` in addition to `===`. This is important for an expression like: `expect {}.to change { a.class }.from(ClassA).to(ClassB)` because `SomeClass === SomeClass` returns false. (Myron Marston) [#]## 2.14.1 / 2013-08-08 [full changelog](http://github.com/rspec/rspec-expectations/compare/v2.14.0...2.14.1) Bug fixes
* Ensure diff output uses the same encoding as the encoding of the string being diff\'d to prevent `Encoding::UndefinedConversionError`
* Wed Jul 31 2013 cooloAATTsuse.com- updated to version 2.14.0 Bug fixes
* Values that are not matchers use `#inspect`, rather than `#description` for documentation output (Andy Lindeman, Sam Phippen).
* Make `expect(a).to be_within(x).percent_of(y)` work with negative y (Katsuhiko Nishimra).
* Make the `be_predicate` matcher work as expected used with `expect{...}.to change...` (Sam Phippen). [#]## 2.14.0.rc1 / 2013-05-27 [full changelog](http://github.com/rspec/rspec-expectations/compare/v2.13.0...v2.14.0.rc1) Enhancements
* Enhance `yield_control` so that you can specify an exact or relative number of times: `expect { }.to yield_control.exactly(3).times`, `expect { }.to yield_control.at_least(2).times`, etc (Bartek Borkowski).
* Make the differ that is used when an expectation fails better handle arrays by splitting each element of the array onto its own line. (Sam Phippen)
* Accept duck-typed strings that respond to `:to_str` as expectation messages. (Toby Ovod-Everett) Bug fixes
* Fix differ to not raise errors when dealing with differently-encoded strings (Jon Rowe).
* Fix `expect(something).to be_within(x).percent_of(y)` where x and y are both integers (Sam Phippen).
* Fix `have` matcher to handle the fact that on ruby 2.0, `Enumerator#size` may return nil (Kenta Murata).
* Fix `expect { raise s }.to raise_error(s)` where s is an error instance on ruby 2.0 (Sam Phippen).
* Fix `expect(object).to raise_error` passing. This now warns the user and fails the spec (tomykaira). Deprecations
* Deprecate `expect { }.not_to raise_error(SpecificErrorClass)` or `expect { }.not_to raise_error(\"some specific message\")`. Using these was prone to hiding failures as they would allow _any other error_ to pass. (Sam Phippen and David Chelimsky)