Wordpress

History

Helen Hou-Sandi 357c1c0b86 Post Formats: You have to pass an array of supported post formats. This shows a `_doing_it_wrong()` message and also returns false instead of true if no array of formats is passed in `add_theme_support()`, avoiding a PHP error. Post formats maintainership comes full circle. 🙃 Props Mista-Flo, sproutchris, garrett-eclipse. Fixes #51390. git-svn-id: https://develop.svn.wordpress.org/trunk@49344 602fd350-edb4-49c9-b593-d223f7449a82		2020-10-27 19:58:10 +00:00
..
data	Block Editor: Update the WordPress packages for 5.6 beta 2	2020-10-27 09:32:50 +00:00
includes	Block Editor: Fix WP_Block_Supports class compatibility with Gutenberg-provided class.	2020-10-26 08:29:04 +00:00
tests	Post Formats: You have to pass an array of supported post formats.	2020-10-27 19:58:10 +00:00
README.txt	…
build.xml	…
multisite.xml	…
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.