Changeset 760 in tests for trunk/README.txt
- Timestamp:
- 06/30/2012 05:30:59 PM (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/README.txt
r751 r760 7 7 3. $ svn up 8 8 9 4. $ php wp-test.php9 4. $ phpunit path/to/test_case.php 10 10 11 11 Notes: 12 12 13 Test cases live in the 'wp-testcase' subdirectory. All files in that directory will be included by default. Extend the WP TestCase class to ensure your test is run.13 Test cases live in the 'wp-testcase' subdirectory. All files in that directory will be included by default. Extend the WP_UnitTestCase class to ensure your test is run. 14 14 15 wp-test.phpwill 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.15 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. 16 16 17 17 The test database will be wiped clean with DROP TABLE statements once tests are finished, to ensure a clean start next time the tests are run. 18 18 19 wp-test.phpis intended to run at the command line, not via a web server.19 phpunit is intended to run at the command line, not via a web server.
Note: See TracChangeset
for help on using the changeset viewer.