cfeae751a0
`test_revision_order()` was written ([28541], #26042) to ensure that revision order was properly preserved in two different cases: (1) where the post_date varied (in which case the revisions would be sorted by post_date DESC) and (2) where the post_date was the same (in which case sorting would fall back on ID DESC). In an attempt to ensure that both of these scenarios arose in the context of a single test, 100 posts were created. We can make the process far more efficient by manually creating the revisions with the post_dates explicitly declared, and splitting the two different cases into two separate test methods. This test was previously the single worst offender in the entire suite, taking upwards of 15 seconds to run. All that most maddens and torments; all that stirs up the lees of things; all truth with malice in it; all that cracks the sinews and cakes the brain; all the subtle demonisms of life and thought; all evil, to crazy Boone, were visibly personified, and made practically assailable in `test_revision_order()`. See #30017. git-svn-id: https://develop.svn.wordpress.org/trunk@30511 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.