sergiotarxz/Wordpress
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
bf6a689c65
Wordpress/tests/phpunit
History
rachelbaker bf6a689c65 REST API: Include the status property in view context responses from the Posts endpoints. 
Previously the status for a Post (or other post_types) was only exposed under the `edit` context, which doesn't really make much sense considering we support querying by post status without authentication. Originally introduced in v2.0 beta 1: 69f617d749 without any explanation in the commit message.

Props dhanendran, jnylen0, rachelbaker.
Fixes #39466.


git-svn-id: https://develop.svn.wordpress.org/trunk@40080 602fd350-edb4-49c9-b593-d223f7449a82
2017-02-19 04:31:12 +00:00
..
data Tests: Replace broken codeispoetry.png file. 2017-01-11 16:24:30 +00:00
includes REST API: Include the status property in view context responses from the Posts endpoints. 2017-02-19 04:31:12 +00:00
tests REST API: Skip generating the client test fixtures in multisite mode. 2017-02-18 19:29:24 +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 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.