wlsf82 / wlsf82/gitlab-cypress
Investigate flakiness on "Closes an issue" test
Open
Nobody has claimed this yet.
good first issue
help wanted
- Dominant language
- JavaScript
- Stars
- 105
- Forks
- 30
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
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
Start by opening the referenced Cypress Cloud run and examining the "Closes an issue" test and its failure details. Trace that test in the repository to reproduce the flakiness; done means identifying the intermittent cause and documenting or fixing it with a reliable test result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100