wordpress-develop

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

History

Sergey Biryukov c558823416 Tests: Remove multiple `$wpdb::placeholder_escape()` calls in `wpdb` tests. This aims to improve performance of the tests by reducing the number of function calls. Since `$wpdb::placeholder_escape()` saves the result in a static variable on the first run, there is no need for repeated function calls during the same request or test run, as the result would still be the same. Follow-up to [42056]. See #55652. git-svn-id: https://develop.svn.wordpress.org/trunk@53577 602fd350-edb4-49c9-b593-d223f7449a82		2022-06-25 14:43:27 +00:00
..
data	Themes: Accept valid block themes.	2022-05-20 00:47:45 +00:00
includes	Tests: Move `assertQueryTrue()` closer to the other custom assertions in `WP_UnitTestCase_Base`.	2022-06-21 11:12:02 +00:00
tests	Tests: Remove multiple `$wpdb::placeholder_escape()` calls in `wpdb` tests.	2022-06-25 14:43:27 +00:00
build.xml	Coding Standards: Replace spaced indentation sections of `phpunit.xml.dist`, `multisite.xml`, and `build.xml` with tabs.	2019-01-28 17:20:06 +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	Code Modernization: Replace `dirname( __FILE__ )` calls with `__DIR__` magic constant.	2020-02-06 06:31:22 +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.