Wordpress

History

Boone Gorges 829ae5f4ce Fail gracefully when checking mapped cap against unregistered post type. Post type objects are reponsible for mapping their capabilities to core caps. As a result, when the post type is no longer registered, the caps are no longer mapped. This causes problems when a post is left in the database after the post type is no longer present, and WP does an 'edit_post' or other cap check against it: a PHP notice is thrown, and the cap check always fails. As a more graceful fallback, we map all post-type-dependent caps onto 'edit_others_posts', which allows highly privileged users to be able to access orphaned content (such as comments belonging to disabled post types), while minimizing the possibility of unintended privilege escalation. We also add a `_doing_it_wrong()` notice, so that developers and site administrators are aware that the cap mapping is failing in the absence of the registered post type. Props mitchoyoshitaka, DrewAPicture, imath, codeelite, boonebgorges, nofearinc, SergeyBiryukov, jorbin, dlh. Fixes #16956. git-svn-id: https://develop.svn.wordpress.org/trunk@34091 602fd350-edb4-49c9-b593-d223f7449a82		2015-09-12 21:26:57 +00:00
..
data	Remove `svn:executable` from test files.	2015-07-26 09:40:58 +00:00
includes	Update PHPMailer to 5.2.10 from 5.2.7.	2015-07-08 17:15:02 +00:00
tests	Fail gracefully when checking mapped cap against unregistered post type.	2015-09-12 21:26:57 +00:00
build.xml
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +00:00
README.txt
wp-mail-real-test.php

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.