For now we seem to worked around this problem by specifying the following code
in a cucumber support file:
require 'minitest/autorun'
require 'test/unit/assertions'
World( Test::Unit::Assertions )
require 'minitest'
module Minitest
attr_accessor :assertions
end
At least, things are no longer blowing up as soon as the feature run starts.
It is yet to be determined whether this is a real fix as we have run into some
other issues with AR-4.1 vis a vis code that runs fine with AR-4.0.
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:byrn...@harte-lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rubyonrails-talk+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rubyonrails-talk/c7cc7121d2da5eb8c59f1ed810485e84.squirrel%40webmail.harte-lyne.ca.
For more options, visit https://groups.google.com/d/optout.
