wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Boone Gorges 7c79386135 Tests: Use the same incrementor for all fields belonging to a given text fixture. [35244] changed the way that `WP_UnitTest_Generator_Sequence()` created an incrementor for object fields (like 'post_name' and 'user_email'), by making incrementor static across the entire run of the test suite. While this helped to enforce uniqueness across the tests, it has the side effect of bumping the incrementor between fields on the same object (so that, eg, the same post might have `post_name` "post-12" but `post_title` "Post 13". By switching to a technique that uses the same incrementor for each field belonging to a given fixture, we conform better to the expectations of developers using `WP_UnitTest_Factory`. Fixes #35199. git-svn-id: https://develop.svn.wordpress.org/trunk@37299 602fd350-edb4-49c9-b593-d223f7449a82		2016-04-22 14:35:52 +00:00
..
data	Tests: Add test for `wp_get_installed_translations()`.	2016-02-17 22:01:11 +00:00
includes	Tests: Use the same incrementor for all fields belonging to a given text fixture.	2016-04-22 14:35:52 +00:00
tests	Smilies: Move `convert_smilies` to happen later in the `the_content` filter.	2016-04-22 07:07:03 +00:00
build.xml	Move PHPUnit tests into a tests/phpunit directory.	2013-08-29 18:39:34 +00:00
multisite.xml	Tests: Add speedTrapListener to multisite's PHPUnit config	2016-04-20 17:01:07 +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.