Wordpress

History

James Nylen 162e1a6f2a REST API: Allow setting post formats even if they are not supported by the theme. A `post_format` not used by the current theme, but supported by core is not a wrong/broken piece of information. It's just not used at this point in time. Therefore we should allow setting and retrieving any of the standard post formats supported in core, even if the current theme doesn't use them. After this commit, a post's `format` value can survive a round trip through the API, which is a good general design principle for an API. Props JPry, iseulde, davidakennedy, Drivingralle. Fixes #39232. git-svn-id: https://develop.svn.wordpress.org/trunk@40120 602fd350-edb4-49c9-b593-d223f7449a82		2017-02-24 23:29:04 +00:00
..
data	Tests: Replace broken codeispoetry.png file.	2017-01-11 16:24:30 +00:00
includes	REST API: Shim `post_date_gmt` for drafts / empty dates in the REST API.	2017-02-24 18:14:21 +00:00
tests	REST API: Allow setting post formats even if they are not supported by the theme.	2017-02-24 23:29:04 +00:00
build.xml
multisite.xml	oEmbed: Remove the oEmbed provider unit tests.	2016-10-20 09:15:10 +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.