-
Notifications
You must be signed in to change notification settings - Fork 5
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
Expand on Cypress Implementation #611
Comments
@kbrey could you help me flesh out the technical requirements on this ticket description? would love to get it groomed & pointed in the next week. thank you so much! |
@sydney-devine & @CalebPena wanted to make y'all aware that we are interested in this! @kbrey is looking into the technical scope right now before we actually assign it to anyone. is that cool? let us know if there's anything we should be aware of with regards to the implementation y'all did in 2023! |
Hey let's chat about it in our meeting next week? I'm not 100% sure what this is related to? |
@sydney-devine sure! it's related to us wanting to standardize our QA process for new features that we're adding. especially for testing new programs and the accuracy of their calculations. we want to leverage cypress to do this. since we found that there was an existing implementation of cypress from Ivonne (linked in the ticket description), we figured that we could expand on that, and wanted a gut check from you and @CalebPena to see if that was cool! |
We want to implement end-to-end (E2E) tests using Cypress, including happy paths and edge cases. This will make it easier to catch potential regressions and bugs early in the development process and improve release confidence. The manual QA regression testing plan can be used as a starting point.
We have an existing implementation from 2023, but may need to adjust it to capture more scenarios https://github.com/Gary-Community-Ventures/benefits-calculator/blob/main/cypress/e2e/user_flow_input_test.cy.js
Requirements:
The text was updated successfully, but these errors were encountered: