-
Notifications
You must be signed in to change notification settings - Fork 7
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
Updated/Modified Cypress test for Unlock Certification #3452
Conversation
Terraform plan for meta No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #2508 |
Terraform plan for dev No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #2508 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against f1c58d6 |
cy.get('#continue').contains('Unlock submission').click(); | ||
cy.get('img[alt="FAC.gov"]').should('exist').click(); | ||
cy.url().should('match', /\/audit\//); | ||
cy.get('table.usa-table.margin-top-0.pa11y-ignore tbody > tr:last-child .usa-link').contains('In Progress').click(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not 100% sure but I feel like we had issues in the past with assuming the last entry is the audit currently being tested. Maybe we can do something like this?
cy.contains('td', reportId)
.siblings()
.contains('td', 'In Progress');
Not tested, just a guess!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point I will look into this, thank you.
In reference to:
Issue: #2998
Issue: #3339
In this PR:
In Progress
tablecross-validation.js
at the end of test since we have to lock it again for certificationScreenshots:
How to test:
Open & Run Cypress locally as you normally would
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)git status | grep migrations
. If there are any results, you probably need to add them to the branch for the PR. Your PR should have only one new migration file for each of the component apps, except in rare circumstances; you may need to delete some and re-runpython manage.py makemigrations
to reduce the number to one. (Also, unless in exceptional circumstances, your PR should not delete any migration files.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.