Wordpress

History

Dion Hulse ade2dd5dfe Tests: Remove redundant `assertEquals()` calls in listFilter tests. As these tests are already validating that two arrays match, checking that the counts also match before is redundant and makes it harder to debug when the test fails. See #16895 git-svn-id: https://develop.svn.wordpress.org/trunk@42526 602fd350-edb4-49c9-b593-d223f7449a82		2018-01-18 05:14:28 +00:00
..
data	Media: Add `small-audio.flac` for a unit test added in [42451].	2018-01-15 22:32:47 +00:00
includes	Build/Test tools: Remove unnecessary PHP functionality tests from the test suite.	2017-12-09 23:08:24 +00:00
tests	Tests: Remove redundant `assertEquals()` calls in listFilter tests.	2018-01-18 05:14:28 +00:00
build.xml
multisite.xml	Tests: Rename ignored tests in `multisite.xml`.	2017-08-18 10:59:38 +00:00
README.txt
wp-mail-real-test.php	Code is Poetry.	2017-11-30 23:09:33 +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.