On Dec 8, 2007 11:47 PM, James Deville <[EMAIL PROTECTED]> wrote: > I figured most of it out. The Spec::Rails stuff was something in the code > which has been fixed by revision 3099. The test methods partially make > sense. Since the test/unit code has been integrated, methods with test in > them are automatically turned into specs. However, the test? method is in a > lib file that isn't directly loaded into the specs. It is a convenience > method: def test?; RAILS_ENV=="test";end > I don't know why this method is being included in my tests, every context > has it as an example. Any ideas? >
I have a couple ideas. If the lib file is on the load path, then maybe rspec is searching it. Also, re: the name, maybe rspec and/or test::unit is recognizing the method as a test because it begins with "test." Try renaming the method. Regards, Craig
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
