-
Notifications
You must be signed in to change notification settings - Fork 881
Integration tests for each UI page #546
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
Comments
I think we are already doing that as we go, I'm not sure if we need a ticket for this @misskniss. @coder/frontend what do you all think? |
Closing this based on the above comment and conversation in slack with the FE team. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a developer I want to create an integration test for each page we build into the UI so that I can be sure that at least the most common happy path(s) are working as we expect them to for our customers.
Integration test definition: Testing a glue component - a component that combines rendering with a larger piece like global state. It does not hit the actual backend (we are mocking the API).
Here is a list of all the V1 pages and sections in the UI now.
Disclaimer: I (Jen) may have a missed a couple things that were state dependent so don't take this as a fully exhaustive list)
This issue may need to be promoted to an Epic.
Once V2 beta planning is complete we need to create a check list in this issue for each page we decide to create for each phase of the product release. Then spin up tickets for the MVP, Migration, and Post-MVP milestones.
The text was updated successfully, but these errors were encountered: