-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FlexMock no longer works with Minitest #15
Comments
Thanks. Looking into this. |
This seems to be a Minitest 4 VS 5 thing. MT4 still ships with Ruby 2, so I have to support that, but MT5 is often installed as a gem. I'm going to have to figure out how to test against both in an automated way. Sigh :{ |
Yeah, chasing MiniTest API changes is difficult. Sadly, they have an under developed mocking framework. |
Under Ruby 1.9.3 I work with a pattern like this:
|
Related to #16 |
A word: I'm trying to take over the maintenance of flexmock. It's unfortunately bit-rotting since Jim's passing, and that's really a pity - both for his memory as a great contributor to Ruby's community and as a really nice piece of software. I've fixed that particular issue, as well as added minitest-specific support and some other things |
It is compatible with pre-5 minitest (as shipped with ruby until at least 2.1) and 5.0+ Note that flexmock's own testsuite currently requires plain ruby, so you can't run the main testsuite if the 5.0+ minitest gem is active Fixes jimweirich#15 and jimweirich#16.
Running flexmock 1.3.2 & Minitest 5.0.6
results in
The text was updated successfully, but these errors were encountered: