Wordpress

History

Eric Andrew Lewis c592a7262e Posts: Non-trashed posts should take slug priority over trashed posts. When determining a unique post slug, trashed posts are taken into account. Previously, new posts would add suffixes to their slugs (e.g. `about-2`) when a post in the trash had the desired slug (e.g. `about`). To avoid this behavior, when a post is trashed its slug (i.e. `post_name`) is now suffixed with `-%trashed%`. The post's pre-trash slug is stored as post meta, and if the post is restored from trash, its desired slug is reapplied. For existing trashed posts which don't have the `-%trashed%` suffix, the suffix is added when a post with its desired slug is created. Props ocean90, boonebgorges, ryan, SergeyBiryukov, coffee2code, helen, williamsba1. See #11863. git-svn-id: https://develop.svn.wordpress.org/trunk@36607 602fd350-edb4-49c9-b593-d223f7449a82		2016-02-21 21:44:14 +00:00
..
data	Tests: Add test for `wp_get_installed_translations()`.	2016-02-17 22:01:11 +00:00
includes	Tests: Add decorators to PHPMailer mock object.	2016-02-20 03:40:49 +00:00
tests	Posts: Non-trashed posts should take slug priority over trashed posts.	2016-02-21 21:44:14 +00:00
build.xml
multisite.xml	Embeds: Add oEmbed provider support.	2015-10-07 10:35:18 +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	Initialise `$_SERVER['SERVER_NAME']` during the test bootstrap to avoid individual tests having to do it.	2015-10-21 23:51:45 +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.