Cypress test errors/warnings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 63
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 15
Description
## Summary
When running cypress tests, the errors/warnings that show up before the tests run is getting bigger. We should go through and fix any of the errors/warnings that we can.
## 💬 Description
From the screenshot above, it seems that most of the issues are probably going to type errors so should be fairly easy to fix.
## 💰 Use value
We're more confident the tests will pass if there's no errors before they run.
## 📝 Acceptance Criteria
If relevant, describe in full detail the different interactions and edge cases that the component or patterns needs to fulfil.
*Given* cypress tests are run
*When* they first load up
*Then* there are no errors
Contributor guide
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
Run the Cypress tests and inspect the errors and warnings shown before the test run, using the linked screenshot as context. Identify which startup issues can be fixed and verify completion when Cypress starts without errors or warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, typescript
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100