WordPress / WordPress/phpunit-test-runner
Error handling and notifications for runner issues
Open
Nobody has claimed this yet.
enhancement
tooling
WCUS26
- Dominant language
- PHP
- Stars
- 77
- Forks
- 77
- Avg merge
- 15d 15h
- Merged PRs (30d)
- 4
Description
If a test runner encounters an error the script quits with no follow up. As such, hosts may not know that their test runners have stopped reporting. Configure better error handling and notifications to reporters when a runner process errors or exits.
- Listen to capture errors that cause scripts to exit
- send the error body and heads up in an email to the test reporter
- send the test failure to wp.org in test results so the hosting team can follow up (currently results are only sent if report.php runs. Often, test.php will error and a report is never sent)
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 tracing test.php and report.php to understand where runner errors currently stop execution and where results are sent. Done means runner errors and exits notify the test reporter by email, and failed tests still reach wp.org when report.php does not run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100