wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2026-04-06 21:54:28 +00:00

Files

John Blackbourn b0754798c6 Revisions: Remove an unnecessary call to _doing_it_wrong() and corresponding new text string from the implementation of the new wp_save_post_revision_revisions_before_deletion filter.

While the guard condition was technically correct, it's not practical or necessary to provide this protection for every use of every filter, and it adds unnecessary burden to translators to provide translations for strings that will likely not be seen.

Follow up to [55254].

Fixes #57320


git-svn-id: https://develop.svn.wordpress.org/trunk@55406 602fd350-edb4-49c9-b593-d223f7449a82

2023-02-22 20:47:38 +00:00

data

REST API: Only use Latin characters in test filenames.

2023-02-17 18:37:24 +00:00

includes

Taxonomy: Implement wp_cache_get_multiple in wp_queue_posts_for_term_meta_lazyload.

2023-02-07 12:07:46 +00:00

tests

Revisions: Remove an unnecessary call to _doing_it_wrong() and corresponding new text string from the implementation of the new wp_save_post_revision_revisions_before_deletion filter.

2023-02-22 20:47:38 +00:00

multisite.xml

Build/Test Tools: Update PHPUnit configuration for PHPUnit 9.5.10/8.5.21+.

2021-09-26 03:11:18 +00:00

README.txt

Docs: Remove double spaces in tests/phpunit/README.txt.

2022-04-29 13:31:48 +00:00

wp-mail-real-test.php

Docs: Align spelling with American English.

2022-10-21 21:10:29 +00:00

README.txt

The short version:

1. Create a clean MySQL database and user. DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed.

2. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name/user/password.

3. $ svn up

4. Run the tests from the "trunk" directory:
   To execute a particular test:
      $ phpunit tests/phpunit/tests/test_case.php
   To execute all tests:
      $ phpunit

Notes:

Test cases live in the 'tests' subdirectory. All files in that directory will be included by default. Extend the WP_UnitTestCase class to ensure your test is run.

phpunit will initialize and install a (more or less) complete running copy of WordPress each time it is run. This makes it possible to run functional interface and module tests against a fully working database and codebase, as opposed to pure unit tests with mock objects and stubs. Pure unit tests may be used also, of course.

Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.

phpunit is intended to run at the command line, not via a web server.