Add travis.yml

Copied from factory_girl.
Add suffix option for Rails config

Closes #78
Add Travis CI status to README
Install gems required by appraisal
Allow a custom directory for factories be specified

Closes #73
Bundle in an attempt to fix travis
Bump Cucumber and Aruba
Initial support for MiniTest

Closes #68, #75
Add minitest-rails to appraisal
Regenerate gemfiles using newer Appraisal naming convention, point travis at correct files
Use minitest-rails only when we actually want to test it.

Some features test the factory_girl_rails integration with minitest-rails.

Other features just test normal integration with rails generators.

When minitest-rails is *always* in our gemfiles, minitest's generator
gets run during the features which generate new rails apps.

Because minitest doesnt support namespaced models, this fails.  But, also,
we don't actually want to run minitest during anything other than the specific
areas where we are testing that integration.

Thus, we need the gem present on the system, but not in the gemfiles during
any times other than when it's pulled in specifically by those features.
Bump the rails 3.2.8 appraisal to 3.2.9
jruby needs a separate sqlite3 adapter
Speed up performance on jruby
Simplify the jdbc sqlite3 driver replacement
Improve the way we switch between project Gemfile and appraisal gemfiles

Previously, the railties required by the project gemspec was in conflict with
the rails versions being pulled in by Appraisal.

There were situations where a newer rails app was generated by `rails new...`
even though the Appraisal gemfiles/ value should have been setting it correctly.

We need to be able to use the versions of things specified in the appraisal gemfiles/
specify the version of rails for the initial generation of the applications,
but subsequently allow those applications to point to the `Gemfile` within
the newly generated rails apps, rather than wherever BUNDLE_GEMFILE was previously
set by Appraisal.
Rails 3.1 adds the Turn gem to the gemfile, which impacts the format that results are reported in, and we must verify that format
Add earlier checks to show when the bundle install within the new rails app goes wrong
Make sure the gems that the rails apps are going to need are in place ahead of time
Instead of modifying the environment, run bundle install in a new process

JRuby does not support setting/unsetting environment variables.

Thus, we will launch an entirely new process without the parents env when
we run `bundle install` inside the generated rails apps, forcing them to
use their own Gemfile, instead of the BUNDLE_GEMFILE setting from the main
gem codebase.