expect_with :rspec endīoth rspec-expectations and the standard library assertions areĪvailable as modules– RSpec::Matchers and Test::Unit::Assertions, configure do | config | # not strictly necessary this is the default config anyway config. RSpec 2 allows you to configure which you want to use: For better or worse, some people really dislike rspec-expectations Test::Unit or minitest, rather than using RSpec's object.should whatever Using RSpec's example definition DSL ( describe, it, before, let,Įtc) while sticking with the assert_foo assertion methods from In particular, it allows people to use rspec-core to define and run their tests This separation opened up new possibilities for people to pick andĬhoose which parts of RSpec they want to use. Besides the fact that decoupling is A Good Thing™, One of the primary goals of RSpec 2 was to decouple the spec runner (rspec-core)įrom the mocking framework (rspec-mocks) and the expectation framework Not sure what the right solution is to the problem I was trying to solveīy making those changes, but I'm hoping that by blogging about it, weĬan get some good ideas from the community. I'm the one who made those changes to RSpec, and people are rightfullyĪnnoyed with these changes…but there's a lot more to the story.
Recently, there have been comments and complaints on these changes Settings ( expect_with and mock_with) are set after defining an Removed, and now an error is raised when particular configuration RSpec 2.6 introduced a deprecation warning when using nfigure after defining an example group. Recent RSpec Configuration Warnings and Errors Myron Marston Nov 4, 2011
0 kommentar(er)
