Regression testing with playwright

[allly-b]

Ticket

Resolves #3583

Changes

• regression testing designed for local running
• Copilot used to help autogenerate the test data
• Not a complete regression test suite yet. Checks: domain request flow to submission on the user side, and through approval on the django admin side. Checks ability to view domain requests and domains, Doesn't check any commands that use EPP (like adding nameservers, putting it on hold, etc), this would require running it in a sandbox
• checks with various permission configurations, hence multiple types of users for different tests.
• MORE changes should be added here but in interest of time leaving this as is

Context for reviewers

Setup

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

• Met the acceptance criteria, or will meet them in a subsequent PR
• Created/modified automated tests
• Update documentation in READMEs and/or onboarding guide

Ensured code standards are met (Original Developer)

• If any updated dependencies on Pipfile, also update dependencies in requirements.txt.
• Interactions with external systems are wrapped in try/except
• Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

• Follow the process for requesting a design review. If code is not user-facing, delete design reviewer checklist
• Verify new pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• Reviewed accessibility checklist using screen reader (such as NVDA with Chrome or Voiceover with Safari), ANDI, or WAVE:
  • Tested general usability
  • Page header structure
  • Landmarks
  • Links and buttons
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

• Pulled this branch locally and tested it
• Verified code meets all checks above. Address any checks that are not satisfied
• Reviewed this code and left comments. Indicate if comments must be addressed before code is merged
• Checked that all code is adequately covered by tests
• Verify migrations are valid and do not conflict with existing migrations

Validated user-facing changes as a developer

Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.

• New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Meets all designs and user flows provided by design/product
• Checked keyboard navigability
• Reviewed accessibility checklist using screen reader (such as NVDA with Chrome or Voiceover with Safari), ANDI, or WAVE:
  • Tested general usability
  • Page header structure
  • Landmarks
  • Links and buttons
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)
• (Rarely needed) Tested as both an analyst and applicant user

As a designer reviewer, I have

Verified that the changes match the design intention

• Checked that the design translated visually
• Checked behavior. Comment any found issues or broken flows.
• Checked different states (empty, one, some, error)
• Checked for landmarks, page heading structure, and links

Validated user-facing changes as a designer

• Checked keyboard navigability
• Reviewed accessibility checklist using screen reader (such as NVDA with Chrome or Voiceover with Safari), ANDI, or WAVE:
  • Tested general usability
  • Page header structure
  • Landmarks
  • Links and buttons
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)
• Tested with multiple browsers (check off which ones were used)
  • Chrome
  • Microsoft Edge
  • FireFox
  • Safari
• (Rarely needed) Tested as both an analyst and applicant user

References

• Code review best practices

Screenshots