Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full tests #145

Open
aars opened this issue Mar 9, 2017 · 0 comments
Open

Full tests #145

aars opened this issue Mar 9, 2017 · 0 comments

Comments

@aars
Copy link
Collaborator

aars commented Mar 9, 2017

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant