wordpress-develop

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

History

Tonya Mork 9b6d04adaa Fonts: Removes static instance in wp_print_font_faces(). The static instance of `WP_Font_Face` is not needed. It was an unnecessary carryover from the experimental Fonts API (which was not introduced into Core). Whereas the Fonts API needed to persist its data (i.e. to maintain the registered and enqueued fonts throughout the web request), Font Face does not have data to persist. Font Face processes the fonts it receives when `WP_Font_Face::generate_and_print( $fonts )` is invoked. Thus, a singleton is not needed. Removing the static reduces the amount of the code in the function and eliminates running its tests in separate processes to ensure a different instance is always used. References: * [https://github.com/WordPress/gutenberg/pull/54228 Gutenberg PR 54228]. Follow-up to [56500]. Props hellofromTonya, costdev. Fixes #59165. git-svn-id: https://develop.svn.wordpress.org/trunk@56540 602fd350-edb4-49c9-b593-d223f7449a82		2023-09-07 17:28:59 +00:00
..
data	Editor: add configurable viewport sizes for fluid typography.	2023-09-07 04:28:45 +00:00
includes	Coding Standards: Remove superfluous blank lines at the end of various files.	2023-09-07 14:57:30 +00:00
tests	Fonts: Removes static instance in wp_print_font_faces().	2023-09-07 17:28:59 +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	Coding Standards: Remove superfluous blank lines at the end of various files.	2023-09-07 14:57:30 +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.