Wordpress

History

Felix Arntz 63eda3b3a4 Multisite: Verify the signup nonce using `wp_verify_nonce()` in `signup_nonce_check()`. Prior to this change, the nonce passed from `wp-signup.php` was verified with a simple comparison. Furthermore in case of failures, `wp_die()` would be called right during the HTML markup being already printed. Now the error message is returned properly, modifying the `WP_Error` object in the passed `$result`. Props herregroen. Fixes #43667. git-svn-id: https://develop.svn.wordpress.org/trunk@42976 602fd350-edb4-49c9-b593-d223f7449a82		2018-04-13 15:29:52 +00:00
..
data	Media: Recognize `.ico` files as displayable images on PHP 5.3+ and allow attachment meta data to be generated for them.	2018-03-05 01:02:20 +00:00
includes	Build/Test Tools: Implement `assertNotWPError()` in appropriate places in the test suite.	2018-03-20 22:34:11 +00:00
tests	Multisite: Verify the signup nonce using `wp_verify_nonce()` in `signup_nonce_check()`.	2018-04-13 15:29:52 +00:00
README.txt	…
build.xml	…
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +00:00
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.