wordpress-develop

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

History

Sergey Biryukov e088de67e8 Tests: Update the terminology used for filter names in `tests_add_filter()`. This commit renames the `$tag` and `$function_to_add` parameters to match the `add_filter()` function signature. Includes: * Renaming the `$tag` parameter to `$hook_name`. * Renaming the `$function_to_add` parameter to `$callback`. * Synchronizing documentation for: * `tests_add_filter()` and `add_filter()` * `_test_filter_build_unique_id()` and `_wp_filter_build_unique_id()` Follow-up to [760/tests], [38582], [43555], [46801], [50807], [52300], [53804], [53805], [55023]. See #56793. git-svn-id: https://develop.svn.wordpress.org/trunk@55025 602fd350-edb4-49c9-b593-d223f7449a82		2023-01-02 00:28:02 +00:00
..
data	Editor: Ensure global styles are rendered for third-party blocks.	2022-10-27 15:39:20 +00:00
includes	Tests: Update the terminology used for filter names in `tests_add_filter()`.	2023-01-02 00:28:02 +00:00
tests	Coding Standards: Add visibility to `Tests_Dependencies::test_enqueue_before_register()`.	2022-12-30 03:29:11 +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.