Wordpress

History

Boone Gorges c1b8f1f72a In `Walker_CategoryDropdown::start_el()`, cast values to strings before deciding whether to append 'selected' attribute. As of [32484], `wp_dropdown_categories()` uses the `$value_field` value to decide whether a given `<option>` should be 'selected'. However, `$value_field` can refer to a value that is a string, such as a category's slug. This causes problems when doing a loose comparison (`==`) with the value of the `'selected'` parameter, which defaults to `0`, because when doing a loose comparison between an integer and a string, PHP will cast the string to an integer. This creates false matches, resulting in `<option>` elements getting a 'selected' attribute incorrectly. We address the issue by casting the comparison values to strings, and then using the strict comparison operator `===`. Fixes #33452 for trunk. git-svn-id: https://develop.svn.wordpress.org/trunk@33681 602fd350-edb4-49c9-b593-d223f7449a82		2015-08-21 01:10:34 +00:00
..
data	Remove `svn:executable` from test files.	2015-07-26 09:40:58 +00:00
includes	Update PHPMailer to 5.2.10 from 5.2.7.	2015-07-08 17:15:02 +00:00
tests	In `Walker_CategoryDropdown::start_el()`, cast values to strings before deciding whether to append 'selected' attribute.	2015-08-21 01:10:34 +00:00
build.xml
multisite.xml	Move tests for ms_files_rewriting to separate group, ms-files	2014-11-08 21:07:05 +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

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.