RSpec must require Mocktail before adding DSL? about mocktail

[searls]

Sorry for not getting back to you about this forever—do you have require: false in your Gemfile?

[kevin-j-m]

When I originally reported this, it was from adding to a gem as a development dependency in the gemspec. I found if I require the library, then I would avoid the NameError.

Revisiting this now, I moved it out of the gemspec and into the Gemfile, to be consistent with the README. I moved it out of the test group. I also added require: false.

In all of those scenarios, I'd see the NameError unless I require the library in the spec_helper.

Now, for caveats, this isn't a "real" gem. It's a repo I have that has some example code for a conference talk, so it may not be the best use case. It was the thing I had most easily on hand that I could link public commits to about progress on, and that's why I picked it a while ago to give this library a try.

If no one else is reporting this and aren't having issues with the README instructions using rspec, I have no issue with closing this.

[searls]

While I don't know what you might be running into, I want to make sure there's not something wrong here—mocktail has almost no usage yet because we haven't been explaining or promoting it much.

AFAICT, the library "requires itself" (a misnomer) in the sense that everything that needs to be loaded is in the conventionally-expected place (lib/mocktail.rb), so I'm a little fuzzy on what might be wrong here.

I mean, I presume if you haven't done something to require "mocktail", then of course Mocktail::DSL isn't defined. Is there something else going on here?

[kevin-j-m]

Is the expectation that users should need to require "mocktail" before using it?

If so, do you think adding that info to the Ready to order? section of the README would be helpful? That's part of what I was asking in my (likely poorly worded) initial issue comment.

If not, I may have an issue or something funny going on with my usage.

Thanks for the follow-up! I'm looking forward to seeing this more and more in the community as a former Mockito user/fan. Great stuff here.

[searls]

Thanks Kevin. Going to close this as I don't think this indicates an issue beyond needing to make sure the library is required