Clarify how to handle tests, currently most (if not all) e2e tests in selenium would become obsolete, should probably be followed up by cypress tests
Open
Nobody has claimed this yet.
1. to develop
enhancement
tests
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Subtask to #40172
Clarify how to handle tests, currently most (if not all) e2e tests in selenium would become obsolete, should probably be followed up by cypress tests
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
Start by reading parent issue #40172 and reviewing the Selenium end-to-end tests affected by the proposed change. Done means documenting an agreed testing approach that identifies obsolete tests and any follow-up coverage needed in Cypress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, javascript
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100