API to express expected outcomes of a code example
https://github.com/rspec/rspec-expectations
rspec-expectations provides a simple, readable API to express expected
outcomes of a code example.
- Devel package for openSUSE:Factory
-
11
derived packages
- Links to openSUSE:Factory / rubygem-rsp...pectations
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:ruby:extensions/rubygem-rspec-expectations && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| rspec-expectations-2.12.0.gem | 0000079360 77.5 KB | |
| rubygem-rspec-expectations.changes | 0000001791 1.75 KB | |
| rubygem-rspec-expectations.spec | 0000002409 2.35 KB |
Revision 3 (latest revision is 60)
Stephan Kulow (coolo)
committed
(revision 3)
- updated to version 2.12.0
Enhancements
* Colorize diffs if the `--color` option is configured. (Alex Coplan)
* Include backtraces in unexpected errors handled by `raise_error`
matcher (Myron Marston)
* Print a warning when users accidentally pass a non-string argument
as an expectation message (Sam Phippen)
* `=~` and `match_array` matchers output a more useful error message when
the actual value is not an array (or an object that responds to `#to_ary`)
(Sam Phippen)
Bug fixes
* Fix `include` matcher so that `expect({}).to include(:a => nil)`
fails as it should (Sam Phippen).
* Fix `be_an_instance_of` matcher so that `Class#to_s` is used in the
description rather than `Class#inspect`, since some classes (like
`ActiveRecord::Base`) define a long, verbose `#inspect`.
(Tom Stuart)
Comments 0