[TODO] Set up a standard test runner - remove some custom test code
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Less tests are currently run using a custom test runner. It's possible this could be updated to Vitest, but ideally the test runner would work with Puppeteer (or Playwright) - (I'm not sure if such a test runner exists.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files or existing tests. Start by locating the custom test runner and compare whether Vitest, Puppeteer, or Playwright can support the current tests. Done means the custom runner is replaced by a standard runner that works with the project's required browser tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright
- Domain
- testing-qa, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100