Wordpress

History

Boone Gorges f14dc03ad6 Simplify pagination logic in `comments_template()`. [34561] "fixed" the problem of newest-first comments showing fewer than 'per_page' comments on the post permalink when the total number of comments was not divisible by 'per_page'. See #29462. But this fix caused numerous other problems. First, comment pages reported by `get_page_of_comment()` (which expects comment pages to be filled oldest-first) were no longer correct. Second, and more seriously, the new logic caused comments to be shifted between pages, making their permalinks non-permanent. The current changeset reverts the changed behavior. In order to preserve the performance improvements introduced in [34561], an additional query must be performed when 'default_comments_page=newest' and 'cpage=0' (ie, you're viewing the post permalink). A nice side effect of this revert is that we no longer need the hacks required to determine proper comment pagination, introduced in [34561]. See #8071. See #34073. git-svn-id: https://develop.svn.wordpress.org/trunk@34729 602fd350-edb4-49c9-b593-d223f7449a82		2015-10-01 03:10:13 +00:00
..
data	Add test image for test_exif_keywords test	2015-09-22 21:42:45 +00:00
includes	Fix db_version juggling during non-multisite tests.	2015-09-30 13:27:09 +00:00
tests	Simplify pagination logic in `comments_template()`.	2015-10-01 03:10:13 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Exclude external HTTP tests from multisite run	2015-09-28 02:36:23 +00:00
README.txt	Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .	2013-08-31 13:42:56 +00:00
wp-mail-real-test.php	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00

README.txt

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.