-
Notifications
You must be signed in to change notification settings - Fork 129
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
Figure out an end-to-end testing approach #63
Comments
Going over your open tickets, I saw this one. What about creating a full-featured
That would not cover everything but would be a good start. |
That will cover part of it but not all. We need to test that decK is smart enough to handle cases where it can detect differences and out of sync cases, do reverse syncs too. If you wish to contribute what you are suggesting, that would be a good addition. PR welcome! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Some thoughts/questions?
|
decK v0.5.0 had a very simple bug that rendered the release unusable.
This could have been easily could with an automated end-to-end testing setup, which we don't have at the moment.
As more changes are introduced, manual testing is becoming more expesive and proving not to be sufficient.
Figure out a path forward for how do we want to test decK in an automated fashion.
The text was updated successfully, but these errors were encountered: