The problem is not using or not using the `sample_data`. What's the advantage of testing `claim_objects` with a fake data structure that also has a key value pair `job_json(testrun={"date": "1330454755"})` that isn't part of the json structure we're dealing with in treeherder? I think `job_json` is useful if you're testing conditional handling of one of the attributes where you need to set it to different values and expect different application behavior. When you want a representative structure and there's no differential handling of attributes on the json object I think using real representative data is safer. I've run into this problem in datazilla many times where the generated sample data doesn't really represent the production data, the test passes in development but the the functionality fails in production...