wordpress-develop

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

History

Sergey Biryukov 0e442c4615 Build/Test Tools: Remove the Composer lock file from version control. This makes it easier to run unit tests against multiple different PHP versions. There is currently no reason to have a `composer.lock` file as: * External runtime dependencies are not managed via Composer. * Managed updates of the non-runtime dependencies can be done by locking the version used in the `composer.json` file to a precise version instead of using a `composer.lock` file. * Having the `composer.lock` file in place makes it a lot more difficult to run the tests against all supported PHP versions. With these considerations in mind, the lock file is now removed from version control and added to `.gitignore` and `svn:ignore`. Version constraints for the current dev dependencies are adjusted accordingly: * PHPUnit now explicitly declares in its version constraints that PHPUnit 5.x, 6.x, and 7.x are supported. The minimum supported version for PHPUnit 5.x has been raised from 5.4 to 5.7, which in practice was already the version used for running the tests on PHP 5.6. * PHPCompatibilityWP is effectively updated to version 2.1.2 with the positive impact that a few new constants polyfilled in WP 5.8 are now accounted for (excluded from being flagged). * PHP_CodeSniffer is declared as an explicit dependency to ensure that updates to it will always be explicitly managed instead of inherited. * The DealerDirect Composer plugin is effectively updated to version 0.7.1 without impact. Follow-up to [42960], [46290], [47881], [48957]. Props jrf, johnbillion, desrosj, ayeshrajans, aristath, hellofromTonya, SergeyBiryukov. See #47381. git-svn-id: https://develop.svn.wordpress.org/trunk@51543 602fd350-edb4-49c9-b593-d223f7449a82		2021-08-04 18:55:38 +00:00
..
data	Build: Split packages and blocks to their webpack configs	2021-07-28 10:05:01 +00:00
includes	Build/Test Tools: Remove the Composer lock file from version control.	2021-08-04 18:55:38 +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	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +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.