Wordpress

History

Felix Arntz 08564b5a80 General: Fix problematic string to array parsing. WordPress has historically often used code like `preg_split( '/[\s,]+/', $var )` to parse a string of comma-separated values into an array. However, this approach was causing an empty string to not be parsed into an empty array as expected, but rather into an array with the empty string as its sole element. This was among other areas causing problems in the REST API where passing an empty request parameter could cause that request to fail because, instead of it being ignored, that parameter would be compared against the valid values for it, which typically do not include an empty string. Props david.binda, sstoqnov. Fixes #43977. git-svn-id: https://develop.svn.wordpress.org/trunk@44546 602fd350-edb4-49c9-b593-d223f7449a82		2019-01-10 21:05:50 +00:00
..
data	Upload: Add test files for phpunit.	2019-01-07 20:52:35 +00:00
includes	Tests: Add support for a `WP_TESTS_SKIP_INSTALL` environment variable.	2019-01-10 02:18:19 +00:00
tests	General: Fix problematic string to array parsing.	2019-01-10 21:05:50 +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	Code is Poetry.	2017-11-30 23:09:33 +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.