Closed zedtux closed 9 years ago
It looks like minitest is being loaded, which means that https://github.com/cucumber/multi_test/blob/master/lib/multi_test.rb#L3 is not doing its job properly.
Can you give us some more info about your project @zedtux? Which Ruby version? Can we see your Gemfile?
Ideally, if you could put together a representative GitHub repo, then we can reproduce it ourselves.
Which Ruby version?
Always the latest. Currently 2.1.5.
Can we see your Gemfile? ... Ideally, if you could put together a representative GitHub repo, then we can see how to reproduce it ourselves.
Well the project is private so I can't do that but I can try to create another repo and reproduce the issue. I'll keep you informed.
@zedtux did you manage to create a minimal repository demonstrating this?
Sorry @tooky I will try by tomorrow or during next week.
@zedtux that would be great. Thanks.
@mattwynne @tooky I've tried to upgrade my brewformulas.org project to the latest version of all the gems, including the version 2.0.0.rc3
of Cucumber and I don't see the reported issue.
Or I don't have this issue in this project or the issue has been solved since.
I can try with the version 2.0.0.beta3
in order to check if the issue is present or not.
Well I have this error with the beta 3:
lib/cucumber/mappings.rb:208:in
<class:MapStep>': undefined method
initializer' for Cucumber:Module (NoMethodError)
Yeah that's probably because of an incompatibility in the new version of the core with that beta version of cucumber. To be honest, I suggest we just close this and move on with our lives. If it comes up again we can tackle it then.
OK with you @zedtux?
I'm fine and I do it :)
Thanks @zedtux!
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Therefor there is an issue as I have always the following output at the end of the executing of my tests no matter the test pass or not:
This return a code different than 0 so mark my build as failed while it should not.
This behaviour seems to be since the use of the 2.0.0.beta.3. With my branch I don't have this issue.