Wordpress

History

Boone Gorges 0338c8b3a3 Query: Allow a seed value to be passed when using 'rand' `$orderby`. `WP_Query` allows random ordering; `'orderby' => 'rand'` translates to `ORDER BY RAND()`. This syntax results in random ordering that is not consistent from request to request. MySQL supports the passing of a seed value to random sorts, such as `ORDER BY RAND(3)`, which will return the same random value each time it's called. `WP_Query` now supports this syntax, by passing `RAND(3)` (or whatever integer seed value you'd like) as the value of `'orderby'`. Props hlashbrooke. Fixes #35692. git-svn-id: https://develop.svn.wordpress.org/trunk@36632 602fd350-edb4-49c9-b593-d223f7449a82		2016-02-23 16:39:50 +00:00
..
data	Tests: Add test for `wp_get_installed_translations()`.	2016-02-17 22:01:11 +00:00
includes	Tests: Add decorators to PHPMailer mock object.	2016-02-20 03:40:49 +00:00
tests	Query: Allow a seed value to be passed when using 'rand' `$orderby`.	2016-02-23 16:39:50 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Embeds: Add oEmbed provider support.	2015-10-07 10:35:18 +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	Initialise `$_SERVER['SERVER_NAME']` during the test bootstrap to avoid individual tests having to do it.	2015-10-21 23:51:45 +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.