mirror of
https://github.com/gosticks/wordpress-develop.git
synced 2025-10-16 12:05:38 +00:00
Includes the following fixes: - [Block Library]: Less warnings when blocks try to render themselves. - Reset z-index on focused widget form - Refactor appender margin. - Fix slash inserter for widgets screen. - Widget screens: set html block as freeform content handler. - Widget Block: widget_id is undefined when a widget is placed. - Add <CopyHandler> to WidgetAreasBlockEditorProvider - Add width: 100% to components-base-control inside wp-block-legacy-widget - [Widgets editor] Replace the "technical" error notice a more user-friendly one - Fix legacy widget height overflow - Fix "Select all" behavior in the editor - Increase specificity of the NoPreview CSS rules to avoid conflicts with theme styles - Fix move to widget area checkmark - Replace legacy widget icon with its new version - [Block Library - Query Loop]: Set default block variations not to inherit from global query See #53397. git-svn-id: https://develop.svn.wordpress.org/trunk@51344 602fd350-edb4-49c9-b593-d223f7449a82 |
||
|---|---|---|
| .. | ||
| data | ||
| includes | ||
| tests | ||
| build.xml | ||
| multisite.xml | ||
| README.txt | ||
| wp-mail-real-test.php | ||
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.