error: minitest version out of date

[quinn]

Seems like a strange error message when referring to the latest version of minitest. Was MiniTest::Unit::runner= removed at some point?

[trans]

What version of minitest are you running?

[trans]

If it is v5.0, it is b/c the Mintest API has totally changed (again). Are there any volunteers that want to update/rewrite the adapter code?

[quinn]

Yes, I was using 5.0.4. I think I'll stick with 4.x for the time being.

On Thu, Jun 13, 2013 at 10:44 AM, 7rans notifications@github.com wrote:

If it is v5.0, it is b/c the Mintest API has totally changed (again). Are
there any volunteers that want to update/rewrite the adapter code?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/122#issuecomment-19409963
.

[TvL2386]

I just updated from 4.7.0 to 5.0.6, same error. I'll also be sticking to 4.x for the time being.

[TvL2386]

Wouldn't it be wise for turn to depend on something more specific than 'minitest >= 0'. That would have prevented this error.

EDIT: Correction: It's not a gem dependency I see... Excuse me.

[trans]

I am currently working on the tapout adapter, minitap. When that's finished, I'll use the knowledge gained to write a new turn adapter. But I can't make any promises on the time frame. It's low on the priority list. If anyone else wants it sooner rather than later, please jump in. I'd be more than happy to assist. Barring unforeseen difficulties, it's more or less just a day project.

[glesage]

Seems it's a problem again with Rails 4.1 /:
I get MiniTest v5.3.2 is out of date.

[prodigerati]

Same for me when upgraded to rails 4.1 from rails 4.0.4

Minitest v5.3.3 is out of date

[damienbrz]

Got the same problem with Sinatra

[bmcharek]

Same here. Any chance this will be resolved soon?
cheers

[elfassy]

/lib/turn/minitest.rb:22 MiniTest v5.3.4 is out of date.

[trans]

This is simply because Turn was written for the older Minitest API (which was basically no API at all and relied on class patching). Turn needs to be updated to work for the new Minitest v5 API (an actual API, wow!). Unfortunately I don't have the time to do it right now. And the new maintainers, for whatever reason, haven't gotten to it either (understandably it is not so easy to wrap ones mind around pre-existing code). If I manage to carve out a few days sometime soon I will make an effort to fill it with this task. But for the moment I can't make any promises.