-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Warn if integration using mocha/{test_unit,minitest} fails #389
Warn if integration using mocha/{test_unit,minitest} fails #389
Conversation
Unfortunately #229 didn't really explain the issue thoroughly enough. I've updated the description of that issue to explain why we're not yet ready to apply the changes in this PR. |
Also I was imagining using Ruby's |
Would it help if I changed the message from:
to
for minitest and a similar change for test-unit, i.e. not including the specific I think it'll be less/not confusing then, and will be more helpful than silence for someone whose test library integration has failed. Even otherwise, I think it's more helpful to warn someone for whom the integration has failed than to avoid what a tiny (IMO) bit of confusion for someone who tried to integrate using the legacy/undocument |
I'm away at the moment, but I'll look at this as soon as I get time. Sorry for the delay. |
I've belatedly realised that I was confused in my previous comments on this PR. I had confused I also agree that it's sensible to use deprecation warnings in this PR as a first step; then as a later step we can fail fast. I don't know what I was thinking when I suggested using Sorry for all the confusion. I will get this merged shortly. |
Tweaked very slightly and merged in c6032d0. Closing. |
These were not namespaced and it turns out they aren't actually tested in the build.
As suggested in #229