WordPress / WordPress/plugin-check
Evaluate using proper loopback requests for runtime checks
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 362
- Forks
- 126
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 22
Description
The runtime checks right now are not really smart, they just modify the global WP_Query to "navigate to" specific URLs and then see what kind resources were enqueued/inserted etc. That will never be as accurate as an actual HTTP request to the frontend.
This won't be very straightforward though, because for the runtime checks PCP spins up a separate WordPress install that doesn't affect the main site. So the system under test (SUT) won't actually be accessible via loopback request out of the box. But there might be some ways to address that, for example with some special query parameters or so.
It could also be more feasible for cases like the GitHub Action with a more closed down environment.
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
No files or tests are named. Start by tracing the runtime-check implementation and the separate WordPress install setup, then compare the GitHub Action environment; done means defining and validating a feasible loopback-request approach that observes frontend behavior without losing test isolation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, php
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100