sergiotarxz
/
Wordpress
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Wordpress/tests/phpunit
History
Boone Gorges d3e463cb84 Taxonomy: Take 'parent' into account when checking for terms with duplicate names. 
Terms with duplicate names are not allowed at the same level of a
taxonomy hierarchy. The name lookup introduced in [34809] did not
properly account for the 'parent' parameter, with the result that
the duplicate-name restriction was tighter than intended (terms
with duplicate names could not be created at different levels of
a single hierarchy).

Props mikejolley.
Fixes #39984.

git-svn-id: https://develop.svn.wordpress.org/trunk@40145 602fd350-edb4-49c9-b593-d223f7449a82
 		2017-03-03 02:49:13 +00:00
..
data Media: Reduce failing uploads following 4.7.1. 2017-02-25 16:07:25 +00:00
includes REST API: Shim `post_date_gmt` for drafts / empty dates in the REST API. 2017-02-24 18:14:21 +00:00
tests Taxonomy: Take 'parent' into account when checking for terms with duplicate names. 2017-03-03 02:49:13 +00:00
README.txt
…
build.xml
…
multisite.xml oEmbed: Remove the oEmbed provider unit tests. 2016-10-20 09:15:10 +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.