WordPress / WordPress/phpunit-test-runner
Find ways to reduce the need for NodeJS
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 77
- Forks
- 77
- Avg merge
- 15d 15h
- Merged PRs (30d)
- 4
Description
Right now the phpunit-test-runner requires node and npm in order to build the artifacts to run the tests. We rely on the grunt file from the wordpress-develop repo but the actual phpunit tests we run don't require any of those artifacts.
Describe the solution you'd like
We should spent some research time to see if we can omit the build process as the phpunit-tests don't require all the artifacts to successfully perform all tests.
Additional context
This was part of the research for #243 as a lot of hosts complained about the extra steps included to have a node environment ready to do all this including the additional time needed.
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 reviewing the phpunit-test-runner artifact build and the referenced wordpress-develop Gruntfile.js. Identify which generated artifacts the phpunit tests actually consume and determine whether the build can be omitted; done means the tests run successfully without requiring Node.js and npm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, php
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100