Full tests #145
Description
I think we need better tests. Some that test the entire chain of adapters, mixins, models, etc. The current unit tests are very fragile and rarely test actual use-cases (with server responses mocked, etc).
What do you guys think? I'm having a bit of trouble wrapping my mind around how that test-setup should look. Maybe blog-admin will suffice, but I believe that needs an actual (mock) backend, since the current proxy setup does not allow saving resources.
Any thoughts on how to set this up? Where to begin?