Wordpress

History

Jonathan Desrosiers 0933882c6e External Libraries: Upgrade PHPMailer to version 6.1.6. Now that WordPress Core supports PHP >= 5.6, the PHPMailer library can be updated to the latest version. The PHPMailer files now reside in a new directory, `wp-includes/PHPMailer`. These files are copied verbatim from the library upstream and will make updating in the future easier. For backwards compatibility, the old files will remain and trigger deprecated file warnings. The PHPMailer class is also now under the `PHPMailer\PHPMailer\PHPMailer` namespace. The `PHPMailer` class in the global namespace has been aliased for a seamless transition. This upgrade also clears up a handful of PHP compatibility issues detailed in #49922. For a full list of changes, see the PHPMailer GitHub: https://github.com/PHPMailer/PHPMailer/compare/v5.2.27...v6.1.6. Props Synchro, SergeyBiryukov, desrosj, donmhico, ayeshrajans. Fixes #41750. git-svn-id: https://develop.svn.wordpress.org/trunk@48033 602fd350-edb4-49c9-b593-d223f7449a82		2020-06-12 15:45:30 +00:00
..
data	REST API: Add additional fields to the themes controller.	2020-06-07 06:44:08 +00:00
includes	External Libraries: Upgrade PHPMailer to version 6.1.6.	2020-06-12 15:45:30 +00:00
tests	External Libraries: Upgrade PHPMailer to version 6.1.6.	2020-06-12 15:45:30 +00:00
build.xml
multisite.xml
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.