Overall, it's fine, but we definitely need to build a better infrastructure around storying tests because this is entirely too simple for the amount of tests we will be moving into this system. If you take a look at the current e2e tests for the rest api, you'll see what I mean (I can show you on Monday). Having them all in a single file is not going to be feasible.

That's fairly easy to do if we rely on just environment variables -- then it's just another suite that runs under python -m unittest smokeand we can have as many files as we deem appropriate.
It's a pain to make unittest and standalone work with command line arguments, though.

Some options:

1. We figure out how to make that work. I'm sure it's possible with custom test loaders/runners.
2. We don't, and happily rely environment variables
3. We have some configuration file somewhere that we can read variables from for the integration tests (this may be useful if we need to parameterize other tests)
4. We move to py.test or nosetests which I believe allow more advanced test configuration.

I'm kind of leaning towards 2, which reduces the overhead of this PR to just "Grabbing the env variables and checking in some starter tests"

Subsumed by #176