mirror of
https://github.com/gosticks/wordpress-develop.git
synced 2025-10-16 12:05:38 +00:00
Update packages to include these bug fixes from Gutenberg: - Navigation: Fix click-button size, submenu directions, scrollbars. - Group - Fix overzealous regex when restoring inner containers - Babel Preset: Update Babel packages to 7.16 version - theme.json: adds a setting property that enables some other ones - Polish metabox container. - Fix submenu justification and spacer orientation. - Fix Gutenberg 11.8.2 in WordPress trunk - Strip meta tags from pasted links in Chromium - Hide visilibility and status for navigation posts - Navigation: Refactor and simplify setup state. - Nav block menu switcher - decode HTML entities and utilise accessible markup pattern - Rename fse_navigation_area to wp_navigation_area - theme.json: adds a setting property that enables some other ones - Revert "theme.json: adds a setting property that enables some other ones" - Skip flaky image block test - WordPress/gutenberg@3c935c4 - React to any errors coming up in gutenberg_migrate_menu_to_navigation_post - Return wp error from wp_insert_post - Fix not transforming logical assignments for packages See #54337. git-svn-id: https://develop.svn.wordpress.org/trunk@52161 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.