wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Felix Arntz d17afcc9dd Bootstrap/Load: Introduce functions to check whether WordPress is serving a REST API request. This changeset introduces two functions: * `wp_is_serving_rest_request()` returns a boolean for whether WordPress is serving an actual REST API request. * `wp_is_rest_endpoint()` returns a boolean for whether a WordPress REST API endpoint is currently being used. While this is always the case if `wp_is_serving_rest_request()` returns `true`, the function additionally covers the scenario of internal REST API requests, i.e. where WordPress calls a REST API endpoint within the same request. Both functions should only be used after the `parse_request` action. All relevant manual checks have been adjusted to use one of the new functions, depending on the use-case. They were all using the same constant check so far, while in fact some of them were intending to check for an actual REST API request while others were intending to check for REST endpoint usage. A new filter `wp_is_rest_endpoint` can be used to alter the return value of the `wp_is_rest_endpoint()` function. Props lots.0.logs, TimothyBlynJacobs, flixos90, joehoyle, peterwilsoncc, swissspidy, SergeyBiryukov, pento, mikejolley, iandunn, hellofromTonya, Cybr, petitphp. Fixes #42061. git-svn-id: https://develop.svn.wordpress.org/trunk@57312 602fd350-edb4-49c9-b593-d223f7449a82		2024-01-19 17:37:05 +00:00
..
data	Themes: Remove memoization from stylesheet and theme directories.	2023-11-20 22:27:17 +00:00
includes	Build/Test Tools: Allow overriding the `WP_UnitTestCase_Base::factory()` method.	2023-12-02 11:56:31 +00:00
tests	Bootstrap/Load: Introduce functions to check whether WordPress is serving a REST API request.	2024-01-19 17:37:05 +00:00
multisite.xml	Build/Test Tools: Remove random_compat from PHPCS and PHPUnit configuration files.	2023-09-24 07:43:50 +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	Coding Standards: Remove superfluous blank lines at the end of various files.	2023-09-07 14:57:30 +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.