Ruby 1.9 doesn't automatically include . in the load path; if we do a require to a relative path (eg a file within spec or test), 1.9 will raise a LoadError because spec or test isn't normally in the load path.
…e set by the parent.
…ttributes The change 1b28476 introduced an issue where projects not using ActiveRecord would fail because the constant wasn't defined. This removes the reliance on ActiveRecord and uses different strategies for building hashes from cucumber tables based on whether the attributes are finding a record in the database or creating an instance with factory girl.
…eRecord (which is a big no-no)