wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2026-04-07 22:24:36 +00:00

Files

Jonathan Desrosiers ab070e219b Block Editor: Add helper functions for displaying the editor.

`use_block_editor_for_post()` and `use_block_editor_for_post_type()` determine if the block editor should be loaded.

`get_block_categories()` and `get_block_editor_server_block_settings()` provide data be included while the block editor is loading.

Props pento.

Merges [43762] to trunk.

See #45110.

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

2018-12-13 20:22:06 +00:00

data

Blocks: Parse blocks when displaying posts.

2018-12-13 18:11:10 +00:00

includes

Blocks: Parse blocks when displaying posts.

2018-12-13 18:11:10 +00:00

tests

Block Editor: Add helper functions for displaying the editor.

2018-12-13 20:22:06 +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

Code is Poetry.

2017-11-30 23:09:33 +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.