WordPress / WordPress/Requests
CI: improve the test running
Open
Nobody has claimed this yet.
Type: testing/chores/QA
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 500
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
For all sorts of reasons it would be good to have some more variation in the test environments on which the tests are run in CI.
Some suggestions/ideas:
- Run some test runs via PHPUnit installed via Composer, others with a PHPUnit PHAR so both autoloading mechanisms are tested.
- Run tests both against Ubuntu as well as Windows OS. Maybe also MacOS ?
- Add test runs with select PHP extensions disabled and potentially some functions disabled.
Think:- Curl vs Fsockopen.
- Decompression tries various PHP methods depending on availability. As the first one is available in the default CI setup, the logic and code for the fall-back methods is never actually tested.
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 reviewing the repository's existing CI configuration and test setup; no specific files or tests are named in the issue. Define a CI matrix covering Composer-installed PHPUnit and a PHPUnit PHAR, Ubuntu and Windows, and selected PHP extension or function variations. Done means the relevant fallback paths and test environments run successfully in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100