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.11.3.gem | 0000077312 75.5 KB | |
| rubygem-rspec-expectations.changes | 0000000846 846 Bytes | |
| rubygem-rspec-expectations.spec | 0000002409 2.35 KB |
Revision 2 (latest revision is 60)
Stephan Kulow (coolo)
committed
(revision 2)
- updated to version 2.11.3
[full changelog](http://github.com/rspec/rspec-expectations/compare/v2.11.2...v.2.11.3)
Bug fixes
* Fix (and deprecate) `expect { }.should` syntax so that it works even
though it was never a documented or intended syntax. It worked as a
consequence of the implementation of `expect` in RSpec 2.10 and
earlier. (Myron Marston)
* Ensure #== is defined on build in matchers so that they can be composed.
For example:
expect {
user.emailed!
}.to change { user.last_emailed_at }.to be_within(1.second).of(Time.zone.now)
Comments 0