wordpress-develop

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

History

Sergey Biryukov 461f7764e4 Build/Test Tools: Use a custom autoloader for the PHPUnit 9.x mock object classes. This prevents the classes from being loaded automatically via the `autoload-dev` directives when a Composer-installed PHPUnit 5.x or 6.x version is used, as that would break the test run. It is expected that this autoloader will be removed soon, as it should no longer be needed when the PHPUnit version constraints are widened. Notes: * The autoloader file will be loaded from the Test bootstrap. * The autoloader will always be registered and directed to queue itself _before_ the Composer autoload file (which will already have been registered). * The autoloader will only actually load the WP copies of the files/classes when PHP 8.0 in combination with PHPUnit 7.x is detected. In all other cases, the autoloader will bow out, which effectively then defers to the Composer autoload file to load the files as shipped with the installed PHPUnit version. Follow-up to [48957], [49037], [51543]. Props jrf. See #47381. git-svn-id: https://develop.svn.wordpress.org/trunk@51544 602fd350-edb4-49c9-b593-d223f7449a82		2021-08-04 19:24:14 +00:00
..
data	Build: Split packages and blocks to their webpack configs	2021-07-28 10:05:01 +00:00
includes	Build/Test Tools: Use a custom autoloader for the PHPUnit 9.x mock object classes.	2021-08-04 19:24:14 +00:00
tests	Build/Test Tools: Revert changes only included for testing purposes.	2021-08-03 15:14:03 +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: Fix code coverage reporting to generate report from `src`.	2021-03-26 13:23:52 +00:00
README.txt
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.