wp-media / wp-media/wp-rocket-e2e
WPR remaining smoke tests automations
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 3
Description
We have those tests to be added to smoke
1- https://wpmediaqa.testrail.io/index.php?/cases/view/20907 => for this it can be like we check that no wpr in debug, we check that no Cron unschedule event error for hook: rocket_ in debug.log too => https://github.com/wp-media/wp-rocket-e2e/issues/350
2- https://wpmediaqa.testrail.io/index.php?/cases/view/16919 => https://github.com/wp-media/wp-rocket-e2e/issues/204
3- https://wpmediaqa.testrail.io/index.php?/cases/view/22325 => https://github.com/wp-media/wp-rocket-e2e/issues/333
4- https://wpmediaqa.testrail.io/index.php?/cases/view/20899
5- https://wpmediaqa.testrail.io/index.php?/cases/view/22268
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 reading linked issues #350, #204, and #333, then review the repository's existing smoke-test automation alongside TestRail cases 20907, 16919, 22325, 20899, and 22268. Done means all five listed cases are covered, including the specified debug.log checks for case 20907.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100