Wordpress

History

joemcgill 2eade6230d Media: Better handling of JOINs when searching filenames. Following [38625], any media searches that already included JOINs, e.g., `tax_queries`, would get trampled when we joined the post meta table to search for filenames. This preserves existing JOINs and also only applies the `_filter_query_attachment_filenames()` filter when a search query is being performed. Props flixos90, joemcgill. Fixes #22744. git-svn-id: https://develop.svn.wordpress.org/trunk@38733 602fd350-edb4-49c9-b593-d223f7449a82		2016-10-05 19:50:02 +00:00
..
data	Themes: Account for uppercase chars when managing themes.	2016-10-03 18:12:57 +00:00
includes	Tests: Reset post-related globals after each test.	2016-09-30 03:15:36 +00:00
tests	Media: Better handling of JOINs when searching filenames.	2016-10-05 19:50:02 +00:00
README.txt	…
build.xml	…
multisite.xml	OEmbed: add unit tests. `@group external-oembed` is not run by default.	2016-08-30 18:54:53 +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.