Wordpress

History

K. Adam White a0ac0ff13d REST API: Apply all relevant block rendering filters when rendering block previews.

Several filters were introduced to the render_block method since the initial implementation of the block-renderer/ endpoints, causing the output of those endpoints to diverge from the rendered content of blocks on the frontend.

Props kadamwhite, TimothyBlynJacobs, miinasikk.
Fixes #49387.


git-svn-id: https://develop.svn.wordpress.org/trunk@47360 602fd350-edb4-49c9-b593-d223f7449a82

2020-02-25 15:03:57 +00:00

data

Administration: Capitalize Trash consistently in various messages and comments.

2020-02-10 04:10:09 +00:00

includes

REST API: Don't assume all item schemas have properties.

2020-02-20 16:56:17 +00:00

tests

REST API: Apply all relevant block rendering filters when rendering block previews.

2020-02-25 15:03:57 +00:00

build.xml

Coding Standards: Replace spaced indentation sections of phpunit.xml.dist, multisite.xml, and build.xml with tabs.

2019-01-28 17:20:06 +00:00

multisite.xml

Docs: Improve inline comments per the documentation standards.

2020-01-29 00:43:23 +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

Code Modernization: Replace dirname( __FILE__ ) calls with __DIR__ magic constant.

2020-02-06 06:31:22 +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.