wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Sergey Biryukov 216a9ef513 Tests: Move the basic `get_block_templates()` test to the dedicated file. Now that the function has its own test class, the remaining test from `Tests_Block_Template_Utils` can be moved to `Tests_Blocks_GetBlockTemplates` for consistency. Includes: * Uncommenting some assertions previously commented out. * Moving the `get_template_ids()` helper method to the top of the class. * Standardizing on `wpSetUpBeforeClass()`/`wpTearDownAfterClass()` in both classes. * Declaring the test theme name as a constant in both classes, since the value is not changed by any of the tests. * Renaming some properties in both classes for clarity. Follow-up to [51003], [52062], [53927], [54184], [54187]. See #55652. git-svn-id: https://develop.svn.wordpress.org/trunk@54198 602fd350-edb4-49c9-b593-d223f7449a82		2022-09-18 13:08:33 +00:00
..
data	Editor: Fix get_block_templates() to get templates for a post type.	2022-09-15 22:26:28 +00:00
includes	Tests: Correct magic methods in `Basic_Object`.	2022-09-07 15:59:16 +00:00
tests	Tests: Move the basic `get_block_templates()` test to the dedicated file.	2022-09-18 13:08:33 +00:00
multisite.xml	Build/Test Tools: Update PHPUnit configuration for PHPUnit 9.5.10/8.5.21+.	2021-09-26 03:11:18 +00:00
README.txt	Docs: Remove double spaces in `tests/phpunit/README.txt`.	2022-04-29 13:31:48 +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.