WordPress / WordPress/phpunit-test-runner
Create simple runner set up shortcut scripts
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 77
- Forks
- 77
- Avg merge
- 15d 15h
- Merged PRs (30d)
- 4
Description
Hosts have expressed that the runner/reporter install is tedious. The Hosting Team can try to lessen that with some short-term solutions while more automation is planned (like Lucas' SSH proposal). For example:
In the diff for PR 256 readme.md line 571 there's an example bash script. That bash script could be part of the runner codebase so hosts don't have to make their own, which reduces the install process by one step.
Some other ideas:
- The first few install steps after creating a dir (clone repo, cd into dir, rename env.default to .env, edit .env) could be in a script instead of manual, with prompts for entering database creds and other variables rather than having folks edit it with vim.
- creating the json and xml and running report.php could be condensed into one file along with cleanup.php
So there could be 3 files that are already in the repo, rather than hosts making the files themselves for cron jobs to call.
This could reduce the amount of steps required, simplify install and testing a little bit for hosts and reduce the amount of time required to set the runner/reporter up.
Thoughts? If folks are on board we can make 3 sub-issues for it.
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 with readme.md around line 571 and the example bash script in PR 256's diff. Review env.default, report.php, cleanup.php, and the described clone, configuration, JSON/XML, reporting, and cleanup steps. The issue needs to be narrowed into defined sub-issues before completion can be measured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, php
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100