Be explicit about username in test that depends on it
Rename Turingbot::TestCase#inject -> #run_command

The name inject isn't really meaningful to me,
so making it more explicit by naming it run_command
Log to $stdout instead of STDOUT so that tests can override it
Extract params_for from run_command
Must require logger to use it (whodathought?)
Add integration test

Uses rack-test to invoke the bot
Uses webmock to mock Faraday's call to the internet
Version constraints on dependencies to mitigate drift

Guess you could say that having Gemfile.lock committed is sufficient,
but I kinda feel like I shouldn't have to grep a generated file to see
what dependencies are.

Also, given that they're just whatever committer had installed in their
environment at the time, treating the lock as the definition seems
capricious.
Integration test showing it skips non-post reqeusts
Cleanup test file a bit