Remove commented-out rcov rake task
Switch from using jeweler to using bundler for building the gem.

This removes jeweler as a dependency and makes the configuration of the gem itself more standard, as bundler is becoming very common to use to build gems.
Renaming the main lib file and directory to match the gem name

Gem naming conventions are a bit loose and unfollowed, but I think for a *-ruby library, it would be best to have the directories and the main file have the same name as the gem, but have the namespace just be Clever.

Reference:
* http://www.intridea.com/blog/2012/3/15/polishing-rubies-part-ii#

Similar examples:
* https://github.com/sosedoff/munin-ruby
* https://github.com/zinenko/vk-ruby
* https://github.com/twilio/twilio-ruby
For rdoc, use the clever-ruby/version file instead of looking for a VERSION file
Specify pessimistically-locked gem versions of the dependencies

This is a best practice for stability:
http://robots.thoughtbot.com/post/35717411108/a-healthy-bundle
Change the name of test files and the test helper file to match ruby test file naming conventions
Remove redundant additions to the loadpath

Rake::TestTask automatically adds lib, and test is being added in the Rakefile so the test_helper does not need to add anything to the loadpath.
Remove unnecessary class Test::Unit::TestCase from the test helper

I'm not sure what the purpose of this was meant to be.
Remove unnecessary requiring of rubygems/bundler

I haven't found this to be necessary anymore; rubygems now ships with ruby and everyone uses bundler.
Require minitest/autorun instead of test/unit

Test/unit is just a shim on top of minitest in ruby 1.9 anyway; in my opinion it's better to require minitest.
Use the latest version of minitest rather than the version that comes with ruby
Remove an unnecessary require 'clever-ruby' from the test file; the test_helper takes care of this
Merge pull request #1 from thinkthroughmath/rubygem_conventions

Rubygem conventions
Merge pull request #3 from thinkthroughmath/test_cleanup

Test cleanup
adding travis
adding build status
need rake
Split tests into unit tests and integration tests.

There are many ways to do this, but in my mind the criteria of deciding whether something is a unit test or an integration test involves:

* How many objects is the test exercising? If it's only one, it's a unit test. More? Integration test.
* Is the test using any dependencies that have latency or the potential to be unreliable like a database or network calls? If so, it's an integration test.
* Does the test take longer than a second to run? If so, it's an integration test.
Add VCR for recording web requests and responses during integration tests

This improves reliability, reproducibility, isolation, and speed of the tests. The cassettes can be rerecorded at any time if they get out of sync with the Clever service.
Factor out setting of the api_key from each of the list tests