-
Notifications
You must be signed in to change notification settings - Fork 0
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
Theme: Testing #14
Comments
Need to brainstorm critical test paths to prioritize. Initial thoughts:
|
Measurement for regressions and bugs using existing tickets. |
PR deployment environment for QA |
These were the tickets we made from last time we discussed this—a good chunk of them are done! Set up infrastructure to allow vitest tests to use a database |
Summary
We're making incredible strides shipping features quickly, but this is resulting in deploying too-frequent regressions and bugs into production. To reduce the impact of these regressions while maintaining our velocity, and to help users and developers be more confident in the app, we'll implement testing standards (both automated and QA) and feature flags.
Core Goals
High-Level Projects
Note: I'm fairly out of my depth here, so this is my best attempt based on our prior discussions.
Technical implementation notes
The text was updated successfully, but these errors were encountered: