Changeset 53310
- Timestamp:
- 04/29/2022 01:31:48 PM (2 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/tests/phpunit/README.txt
r46587 r53310 1 1 The short version: 2 2 3 1. Create a clean MySQL database and user. 3 1. Create a clean MySQL database and user. DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed. 4 4 5 5 2. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name/user/password. … … 15 15 Notes: 16 16 17 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.17 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. 18 18 19 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.19 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. 20 20 21 21 Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.
Note: See TracChangeset
for help on using the changeset viewer.