wordpress

mirror of git://develop.git.wordpress.org/ synced 2025-01-17 21:08:44 +01:00

History

Gary Pendergast b4a6de9997 Database: Throw a notice if wpdb::prepare() is called with an incorrect number of arguments

`wpdb::prepare()` currently gives no information if the number of arguments passed doesn't match the number of placeholders in the query. This change gives an explicit notice that the call was incorrect.

Also fixes an enrelated term meta test that was triggering this new notice.

Props thekt12 for the initial patch.
Fixes #42040.



git-svn-id: https://develop.svn.wordpress.org/trunk@41662 602fd350-edb4-49c9-b593-d223f7449a82

2017-10-02 02:10:14 +00:00

data

Themes: Report theme as broken that sets itself as its parent.

2017-09-26 08:53:20 +00:00

includes

Build/Test tools: Update the WP_PHPUnit_Util_Getopt class for PHP 7.2 compatibility.

2017-09-28 23:14:26 +00:00

tests

Database: Throw a notice if wpdb::prepare() is called with an incorrect number of arguments

2017-10-02 02:10:14 +00:00

build.xml

Move PHPUnit tests into a tests/phpunit directory.

2013-08-29 18:39:34 +00:00

multisite.xml

Tests: Rename ignored tests in multisite.xml.

2017-08-18 10:59:38 +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

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.