While poking at resultdb_api and looking into #134, I've found an instance where the resultsdb code doesn't match the documentation posted at http://docs.resultsdb.apiary.io/

Specifically, the documentation lists status as an optional argument to create_job but the code won't accept calls without a valid status.

Go through the resultsdb code, making sure that the code obeys the posted documentation. Writing a set of functional tests that poke the api would be a good thing to have here. Bonus points for unit tests but we're a bit time crunched as this is holding up stg deployment of taskotron.