Build/Test Tools component

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

Enhance unit tests for persistent object caching in #31491


Test Coverage
Building on wonderboymusic‘s previous static code analysis using Scrutinizer in #33491 we’ll extend this to include test coverage analysis.

Travis CI
We’re already ready for PHP7 when it’s released, but we’ll throw the switch at the same time in #33410, we’re also going to start testing against an array of database versions and vendors including MariaDB, see #30462

Split Gruntfile.js into multiple files in #29883, optimize PNG and SVG image files in #30587, and add comments to files automatically created in #30666.

Furthering our CSS Roadmap and adding CSS linting in #29792 and likewise for SCSS in #26905

There are several documentation mini projects covering using all of the above and improving our Git docs alongside existing SVN documentation.

98 open tickets in the Build/Test Tools component

98 open tickets defect (bug) enhancement feature request task (blessed)
5.3 5 6 0 6
Awaiting Review 14 23 0 1
Future Release 22 12 1 7 0 1 0 0

98 open tickets. Last 7 days: +0 tickets

23 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
  • #34185  Excluding certain PHPUnit test groups results in "Database is dead" notice and tests terminate
  • #36190  Support running grunt phpunit tasks inside Vagrant environments
  • #36786  Can't pass filter names to `MockAction::get_call_count()`
  • #37261  Consider removing the `$start` argument from `WP_UnitTest_Generator_Sequence`
  • #37521  Introduce a procedure for deprecating code used in Unit Tests
  • #38032  dbDelta() unit tests lock on MySQL 8.0
  • #38266  Tests: Use assertSame() when the type of the value in the assertion is important
  • #39159  Add APC to automated test matrix
  • #39998  Remove unneeded use of wpdb_exposed_methods_for_testing
  • #40281  Improve Documentation for HTTP Unit Testing docs
  • #41781  do not forcefully phpunit delete fixtures data performance
  • #42076  Allow the external HTTP tests to run internally
  • #42990  Deprecate WP_UnitTestCase::_make_attachment
  • #44351  Fix "Foreign key constraint is incorrectly formed" when running unit tests
  • #45614  Build Tools: grunt build fails if mu-plugins and uploads directories has many files
  • #46577  Improve tests related to file permissions for privacy export requests privacy
  • #46804  wp-phpunit calls _delete_all_posts() too early during bootstrap
  • #47353  jquery.masonry.js Not Found
  • #47567  Add documentation to spy-rest-server test include docs
  • #47568  Add documentation to the testcase-ajax class. docs
  • #47952  create_and_get() doesn't consider that create() can return a WP_Error
  • #48060  Save sent emails to disk

17 tickets slated for 5.3

View list in Trac

  • #31823  Add ESLint integration javascript
  • #42811  Run a Travis job with the MySQL Extension
  • #43731  Use Webpack + NPM scripts to build all the things
  • #43828  Add JSDoc ESLint script javascript
  • #46110  IE11: JS "Syntax error" related to wp-polyfill-formdata javascript
  • #46152  Add PHPCompatibility checks to test suite coding-standards
  • #46373  Add code coverage tracking
  • #46567  Run AJAX test group for multisite multisite
  • #46815  Add PHPUnit setup to composer.json
  • #47195  Switch WP_UnitTest_Factory_For_Blog->create_object() to use wp_insert_site()
  • #47381  Remove the Composer lock file from version control
  • #47411  Build tools, WPCS: disable line ending check coding-standards
  • #47567  Add documentation to spy-rest-server test include docs
  • #47568  Add documentation to the testcase-ajax class. docs
  • #47749  Build tools: remove all old files when cleaning
  • #47767  Simplify and backport the local environment
  • #47952  create_and_get() doesn't consider that create() can return a WP_Error

98 open tickets

Open bugs: 41. 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: