Build/Test Tools component

The Build/Test Tools component roadmap includes, but not limited to the following:

Recent posts on the make/core blog

View all posts tagged build-test-tools.

Recent posts on the make/test blog

View all posts tagged build-test-tools.

221 open tickets in the Build/Test Tools component

221 open ticketsdefect (bug)enhancementfeature requesttask (blessed)
7.283114
Awaiting Review484858
Future Release2739515
221 open tickets. Last 7 days: +7 tickets

15 tickets that have no replies

View list on Trac
  • #29066  Grunt clean:dynamic task does not delete file/s from /build during grunt watch task
  • #46804  wp-phpunit calls _delete_all_posts() too early during bootstrap
  • #53118  Tests: review of correctly setting output expectations docs
  • #53506  When using the WordPress Development Environment (wpenv) links to missing asset files do not return 404 and are redirected
  • #53842  Review the type of select return values rest-api
  • #56087  Configure Codecov status checks
  • #56785  Automatically catch potential security issues before release
  • #60874  Better Block Management System required
  • #61568  Only share Playground testing details when appropriate
  • #62944  Allow a single theme to be tested/built
  • #64222  Improve the upgrade process for the Twemoji library javascript
  • #64296  Make the workflow file responsible that commits changes to built files more maintainable
  • #64970  Create a GitHub Actions workflow for running visual regression testing
  • #66073  Tests: Let WP_Test_REST_Controller_Testcase reflect read-only routes tests
  • #66139  Build/Test Tools: Prepare for GitHub's default block on `pull_request_target`

26 tickets slated for 7.2

View list in Trac
  • #29792  Grunt: Add a stylelint precommit task to check for CSS syntax errors accessibility css coding-standards
  • #40538  Fix or remove useless PHPUnit tests
  • #62004  Test suite: update the tests for PHPUnit 10/11 and get ready for PHPUnit 12
  • #63914  Reassess the need for the external-http tests
  • #64895  Tests: Reduce usage of assertEquals for 7.2
  • #64958  Copy React vendor scripts from Gutenberg, update version number
  • #65064  Flaky test: test_get_theme_featured_list_api fails with external HTTP unavailability tests
  • #65208  Introduce namespacing for the test classes for 7.2 tests
  • #65278  PHPCS scans can fail after running `build:dev`
  • #65432  CI: Upgrade GitHub Actions to support Node.js 24
  • #65451  Update Node.js to 24.x
  • #65484  Loopback requests fail in the wordpress-develop Docker environment
  • #65621  Tests: Make sure to preserve the contents of the uploads directory
  • #65819  Test tool and unit test improvements for 7.2
  • #65845  GitHub Actions updates and improvements for 7.2
  • #65857  Update/Audit NPM Dependencies for 7.2
  • #65889  Skip PHPUnit runs on CSS- and JS-only pull requests
  • #65893  Many PHPUnit tests are not well isolated tests
  • #65920  Add a plugin compatibility testing workflow to catch fatals with popular plugins before release
  • #66048  Multiple runs of the Test Old Branches workflow in a short period of time can cause a stampede of automatic reruns and Slack notifications
  • #66069  Trim the PHPUnit test matrix to supported MySQL and MariaDB LTS versions, with full coverage on the weekly run
  • #66073  Tests: Let WP_Test_REST_Controller_Testcase reflect read-only routes tests
  • #66074  Tests: Reduce the cost of the heaviest PHPUnit test classes tests performance
  • #66111  Unit test factory should throw exceptions instead of returning WP_Error instances
  • #66117  Build/Test Tools: The database healthcheck pings the unix socket, so it passes before the TCP server is up
  • #66123  Grunt jshint:plugins: Exclude minified files more effectively javascript

221 open tickets

Open enhancements: 90 View list on Trac
Open tasks: 37 View list on Trac
Open feature requests: 11 View list on Trac
Open defects: 83 View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of Core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: