Travis CI

[t-richards]

This PR...

• Enables spec running and gem building on Travis CI 🎉
• Makes a few small tweaks to the .gemspec and Rakefile to get tests running
• Bumps the rspec gem and adds rake

[franciscosanchezsfdc]

Are any of the updates here needed to build the gem outside of travis? It seems this is a request for a very specific tool - quite used - but not totally generic change

[t-richards]

@franciscosanchezsfdc

While I suppose that you don't need any of these changes to build the gem outside of Travis CI, having an automated test & build process that everyone can see is definitely desirable, and does generally support the process of building this gem wherever it happens to be built.

By using Travis CI (or something like it), everyone can easily verify that their commits (a) have passing tests, (b) work against multiple ruby versions, and (c) result in a buildable gem.

The CI platform itself is not particularly important; more importantly, the fact that everyone can see continuous test + build results is necessary.

Travis CI was chosen arbitrarily; it is a free CI service for open source software, and it is currently used by other repositories in the Pardot organization on GitHub.

[t-richards]

Going to close this for now; please let me know if you're interested in CI in the future.