Wordpress

History

Jonathan Desrosiers 83cfc77500 REST API: Allow a user to change the letter casing of their email. When a `PUT` request is performed to update a user, a `rest_user_invalid_email` error is incorrectly being returned when the email exists with different letter casing, even if it belongs to the user being updated. `email_exists()` performs a case insensitive lookup, but the conditional statement following that lookup was performing a strict comparison between the new email and the user’s current email. This changes that comparison to instead compare the user ID returned by `email_exists()` with the user ID being updated. This more closely matches the logic used in `edit_user()` and allows a user to change the letter casing of their email. Props fuchsws, rachelbaker, desrosj. Fixes #44672. git-svn-id: https://develop.svn.wordpress.org/trunk@44641 602fd350-edb4-49c9-b593-d223f7449a82		2019-01-17 21:24:47 +00:00
..
data	Upload: Add test files for phpunit.	2019-01-07 20:52:35 +00:00
includes	Tests: Ensure meta keys are cleaned up after each test.	2019-01-17 04:33:42 +00:00
tests	REST API: Allow a user to change the letter casing of their email.	2019-01-17 21:24:47 +00:00
build.xml
multisite.xml	REST API: Restore Autosaves controller test for multisite.	2018-12-14 00:57:50 +00:00
README.txt
wp-mail-real-test.php	Coding Standards: Ignore the violations of `Generic.NamingConventions.UpperCaseConstantName.ConstantNotUpperCase`.	2019-01-11 06:07:50 +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.