Skip to content

Testing strategy #566

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

Closed
david-crespo opened this issue Dec 13, 2021 · 1 comment
Closed

Testing strategy #566

david-crespo opened this issue Dec 13, 2021 · 1 comment
Labels

Comments

@david-crespo
Copy link
Collaborator

david-crespo commented Dec 13, 2021

I'll write more later, but this is meant to be a place to track discussions about testing.

I'm not happy with where we are right now. I don't think we have enough tests. Unit tests are easy enough, but a lot of our logic is integrated. I used to favor decomposing things into unit-testable things that take mockable onSuccess callbacks and their stateful not-easily-tested wrappers that pass in the true values of those callbacks. But I'm not really into that anymore. I feel like there has to be a way of testing the real app logic without too much pain.

#565 is an entry in the discussion.

@david-crespo
Copy link
Collaborator Author

david-crespo commented Mar 27, 2022

MSW + Playwright settles this for me.

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

No branches or pull requests

1 participant