Build/Test Tools component

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

Recent posts on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)

View all posts tagged build-test-tools.

Recent posts on the make/test blog

View all posts tagged build-test-tools.

183 open tickets in the Build/Test Tools component

183 open tickets defect (bug) enhancement feature request task (blessed)
6.2 10 3 0 5
Awaiting Review 44 44 2 6
Future Release 24 33 1 11

183 open tickets. Last 7 days: +4 tickets

25 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
  • #37261  Consider removing the `$start` argument from `WP_UnitTest_Generator_Sequence`
  • #37521  Introduce a procedure for deprecating code used in Unit Tests
  • #41781  do not forcefully phpunit delete fixtures data performance
  • #46577  Improve tests related to file permissions for privacy export requests privacy
  • #46804  wp-phpunit calls _delete_all_posts() too early during bootstrap
  • #49390  Update Grunt Patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to support saving credentials
  • #49491  Escape command arguments of env:cli before passing to docker-compose
  • #50266  Had to specify mysqlMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. socket to run php automated test docs
  • #50393  Run `composer compat` as a part of `grunt precommit`
  • #51571  Output visible error when npm package is missing a dependency
  • #51784  Build/Test Tools: Consider always running npm install with –no-optional
  • #52088  Add multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site support to the local Docker environment
  • #52615 integration?
  • #53118  Tests: review of correctly setting output expectations docs
  • #53480  Existing config files lost when installing local-env
  • #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
  • #54510  Add a GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. Action workflow which alerts contributors if they propose changes to third party files
  • #54537  Tests: Enable PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher version check once PHP 8.0 compatibility is achieved.
  • #55973  Add .gitattributes file to annotate generated files
  • #56087  Configure Codecov status checks
  • #56800  Tests: Reduce usage of assertEquals for 6.2
  • #57189  The PHP tests initialize very slowly in wp-env
  • #57236  Add $wp_filters to WP_UnitTestCase_Base::_backup_hooks() and ::_restore_hooks()

18 tickets slated for 6.2

View list in Trac

  • #49728  [PHP 8] Prepare for the internal functions throwing `TypeError` or `ValueError` exceptions on unexpected types/values
  • #51898  Docker Env: Check that Docker is running before use
  • #53687  `grunt verify:old-files` incorrectly flagging certain files
  • #54864  Update the object-cache.php in phpunit fixture to support wp_cache_get_multiple
  • #55571  Gallery blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. fixtures in phpunit tests need updating
  • #56070  Use a consistent order of annotations in the test suite
  • #56615  Running `build` scripts on Windows machines produces different results
  • #56658  Make build process compatible with newer versions of NodeJS/npm
  • #56706  Tests: `parent::set_up()` calls `wp_list_pluck()`, causing inaccurate coverage.
  • #56782  PHPUnit tests: Add/improve @covers annotations for WP 6.2 coding-standards
  • #56793  Test tool and unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. improvements for 6.2
  • #56794  Add linting for `gutenberg_*` functions coding-standards
  • #56800  Tests: Reduce usage of assertEquals for 6.2
  • #56882  Backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. several GitHub Action compatibility fixes
  • #57099  Fix Test Class HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. Tags
  • #57151  unittest for wp_check_filetype
  • #57189  The PHP tests initialize very slowly in wp-env
  • #57236  Add $wp_filters to WP_UnitTestCase_Base::_backup_hooks() and ::_restore_hooks()

183 open tickets

Open enhancements: 80 View list on Trac
Open tasks: 22 View list on Trac
Open feature requests: 3 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 triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 ticketticket Created for both bug reports and feature development on the bug tracker..

Contributors following this component: