Consider to be solved by itself -- not likely to happen most of the time though :)
Michael
Bret, this is how you reproduce it.
Some old scripts have "include Watir" which is the culprit.
require 'watir'
include Watir
Can you take a look?
Thanks
1. Don't put "include Watir" at toplevel. I've argued many times before
that this is a bad idea. I think that almost every one who does this
does so out of confusion. They think that it is like "include" in Perl
or "import" in Java, but it isn't. Specifically, Java's import is a
naming convenience that affects the current file. Ruby's include is a
naming conventience that affects the current file AND EVERY OTHER RUBY
FILE. Sorry for the shouting, but what it actually does it take
everything in the Watir module and add them to the base object that is
used by every other Ruby class, module and library. It is much, much
worse than using global variables.
OK, end of rant. In this case it is running into a conflict with the
activesupport package, which Watir recently started using to help
simplify our code base.
If you really want to still use "include Watir" there are two other
workarounds:
2. Move the "include Watir" statement to the specific class where you
need it (e.g. your test case class). This is actually a perfectly
reasonable use of this command.
3. Add a "require 'watir/ie'" to your script after "require 'watir'"
Bret
Can you add this resolution in release notes or somewhere?
Thanks, Bret.
Bret