Wordpress

History

John Blackbourn 9990abec14 Plugins: Introduce singular capabilities for activating and deactivating individual plugins. This introduces the following meta capabilities: * `activate_plugin` * `deactivate_plugin` * `deactivate_plugins` The singular `activate_plugin` and `deactivate_plugin` capabilities are used along with the corresponding plugin name when determining whether or not a user can activate or deactivate an individual plugin. The plural `deactivate_plugins` capability is used in place of the existing `activate_plugins` capability when determining whether a user can deactivate plugins. Each of these new meta capabilities map to the existing `activate_plugins` primitive capability, which means there is no change in existing behaviour, but plugins can now filter the capabilities required to activate and deactivate individual plugins. Fixes #38652 git-svn-id: https://develop.svn.wordpress.org/trunk@41290 602fd350-edb4-49c9-b593-d223f7449a82		2017-08-22 14:01:36 +00:00
..
data	Widgets: Remove image sizes generated during media widget phpunit tests from being version controlled.	2017-05-15 22:58:03 +00:00
includes	General: Improve terminology used when referring to installations of WordPress and its extensions.	2017-08-22 11:51:11 +00:00
tests	Plugins: Introduce singular capabilities for activating and deactivating individual plugins.	2017-08-22 14:01:36 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +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.