As QA , I want the test-results-storage of failed tests to have the debug.log of that failed test
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- ci-cd, testing-qa
Research direction
Start by tracing the automatic e2e run that creates test-results-storage and handles debug.log files. Reproduce or inspect a failed test caused by a debug.log-related error, then verify that the related log is preserved in the corresponding run directory alongside the generated cucumber report.
Written by the indexing model from the issue text.
Description
Currently, if e2e failed due to wp rocket related error in debug.log, we rename the debug.log with failed test name. which is helpful for single manual run. However, for auto e2e, run is automatically so when next run start, it'll clear all debug.log files and those files arenot stored in test-results-storage.
example report: scp [email protected]:~/wp-rocket-e2e/test-results-storage/2026-09-19T03-45-36-828Z/cucumber-report.html 2026-09-19T03-45-36-828Z.html
Given: Auto e2e runs
And: any test failed due to debug.log related error
Then: Expect the related debug.log be in test-results-storage of related test Run
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from wp-media/auto-e2e
-
bug Made by AI
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Auto e2e improvementPossibly taken @Mai-Saad claimed this 48 days ago. OpenReady for review
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in wp-media/auto-e2e
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/node-canvas#2633 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
capricorn86/happy-dom#2594 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
microsoft/monaco-editor#5575 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day