Nils Diefenbach

@AndrewLCarpenter, perhaps you could shine some light on the advantages of the above library; I've had a chance to look through this, and I'm interested in giving this a shot...

Yupp, that's about what I had in mind.# As for the end-to-end tests, we need to assert these with caution, but generally I agree. They'd be a good early indicator...

hm. Perhaps? I'm not sure how to go about it, if you have an idea - shoot!

I've replaced calls to the API for all `API` objects with mocks, and now only check if the defined signature is generated as expected.

I've replaced all calls to the API with mocked objects for the interface tests - sample payloads have been added as well in `tests/payloads.py`. We're only missing the `APIResponse` from...

`APIResponse` was implemented and the tests can now be run. There are still quite a few errors, but work is progressing.

Commit 1332b0812c7ef765ada70aa9ae054af16974de45 eliminated the last error in unittests. They're all failing as expected now for interface tests.

Hey @kvak, Sorry for the slow reply! Yes, indeed this has been requested a couple of times, and I started working on this. The problem is, the library still misses...

@HermanoCrespo , thanks for the contribution! Do you think you could submit a PR for this ? I'm currently swamped and might not have the time to update the function...

https://help.github.com/articles/creating-a-pull-request/ Have a look here!