WordPress / WordPress/phpunit-test-runner
Research and document slow/risky tests
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 77
- Forks
- 77
- Avg merge
- 15d 15h
- Merged PRs (30d)
- 4
Description
danielbachhuber [10:17 AM] I'd like to spend a little bit of time looking at the "slow" and "risky" tests to see if we can do anything about them
[10:18] to someone not intimately involved with core development, slow/risky tests seem like an issue with the environment, not core
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 identifying which tests are classified as slow or risky and investigate whether their behavior comes from the test environment or core code. Document the findings, likely causes, and any recommended actions; the work is done when the slow and risky tests are clearly accounted for.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100