Wordpress

History

Boone Gorges eebe549408 When creating terms, avoid false dupe checks due to accented characters. `wp_insert_term()` doesn't allow the creation of a term when the term `name` is the same as another term in the same hierarchy level of the same taxonomy. Previously, this duplicate check used `get_term_by( 'name' )`, which uses the database collation to determine sameness. But common collations do not distinguish between accented and non-accented versions of a character. As a result, it was impossible to create a term 'Foo' if a sibling term with an accented character existed. We address this problem by using `get_terms()` to do the duplicate check. This query returns all potentially matching terms. We then do a stricter check for equivalence in PHP, before determining whether one of the matches is indeed a duplicate. Props boonebgorges, tyxla, geza.miklo, mehulkaklotar. Fixes #33864. git-svn-id: https://develop.svn.wordpress.org/trunk@34809 602fd350-edb4-49c9-b593-d223f7449a82		2015-10-03 20:24:09 +00:00
..
data	Shortcodes/Formatting: Add PCRE Performance Testing	2015-10-02 04:25:40 +00:00
includes	Tests: Last try: It's redundant to reset permalinks on `tearDown()` if we're already doing it on every `setUp()`.	2015-10-03 19:26:24 +00:00
tests	When creating terms, avoid false dupe checks due to accented characters.	2015-10-03 20:24:09 +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.