Skip to content

Write a playwright test #173

Description

@Atticus29
  • Code review Implement playwright #172
  • Work through the PlayWright docs
  • Identify an area (or two separate areas) of the code where the UI has had reversions in the past (i.e., is brittle) or that you suspect might be vulnerable to reversions, and write at least two playwright e2e tests that ensure that the expected output is there.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions