Hello and welcome to the monthly RSpec update!
Here you can find what the core team is up to, what we are planning,
progress towards our next major release, and how you can help out.
*Theme*
Huge month getting the final breaking changes in for beta2. We are
aiming to get it out before the end of the year. The way things are
progressing this will likely be the last beta before a release candidate.
*Last Month*
* *David: *Made rspec-guard compatible with RSpec 3.
* *John: *First pass at formatter registration reworking.
* *John:*Remove monkey patching! It is now completely optional via the
`expose_dsl_globally` configuration option.
* *Myron "The Machine" Marston:*Improve the integration between
rspec-core and rspec-mocks. This solves a long-standing bug [1],
paves the way to easily support multiple mocking libraries [2],
should perform better, and is generally simpler.
* *Myron:*Add `is_expected` for use in one-liners[3].
* *Myron:* Change rspec-mocks' argument matchers and
rspec-expectations matchers to use `===` rather than `==` for
matching [4][5].
* *Myron: *Fix a few bugs in rspec-mocks related to method visibility,
so that, for example, a verifying double properly uses the same
visibility as the named interface[6].
* *Myron: *Update the rspec-expecations matcher protocol so that it no
longer uses `should` in the method names given we are moving away
from that syntax[7].
* *Myron: *Update the `change` matcher to clarify how it works when
negated[8].
* *Myron: *Help @eloyesp with the new compound matcher feature of
rspec-expecations[9].
* *Myron:*Write up a code spike for allowing matchers to be fully
composable[10].
* *Sam:* Added a `with_message` method call to the `raise_error`
matcher. This allows for more readable matching of error messages.
* *Sam:* Internal fixes to allow RSpec rails to warn about the should
syntax correctly.
* *Sam: *Simplified the error messages on the `be` matcher for `true`,
`false` and `nil`. This should help when debugging against these
singletons*.*
*This Month
*
* *John: *Finish off formatter registrationand notification changes.
* *Myron:*Finish implementing fully composable matchers.
* *Sam:*Warn on use of stubs and mocks in before(:all) blocks. [11]
*How You Can Help*
* *Try the beta!*We are working hard to make this the smoothest major
version upgrade you've ever done. Go to 2.99 first, fix
deprecations, then on to 3. Report any issuesto the github issue
tracker.
Cheers,
Xavier and the RSpec team.
[1] https://github.com/rspec/rspec-mocks/issues/102
[2] https://github.com/rspec/rspec-core/issues/683
[3] https://github.com/rspec/rspec-core/pull/1182
[4] https://github.com/rspec/rspec-mocks/pull/473
[5] https://github.com/rspec/rspec-expectations/pull/381
[6] https://github.com/rspec/rspec-mocks/pull/478
[7] https://github.com/rspec/rspec-expectations/pull/373
[8] https://github.com/rspec/rspec-expectations/pull/376
[9] https://github.com/rspec/rspec-expectations/pull/387
[10] https://github.com/rspec/rspec-expectations/pull/388
[11] https://github.com/rspec/rspec-mocks/pull/449
--
You received this message because you are subscribed to the Google Groups
"rspec" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rspec/52AFBFFA.4010700%40xaviershay.com.
For more options, visit https://groups.google.com/groups/opt_out.
