wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2025-10-16 12:05:38 +00:00

History

Tonya Mork 648eb03768 WPDB: Capture error in `wpdb::$last_error` when insert fails instead of silently failing for invalid data or value too long. Instead of silently failing when attempting to insert a value into a field, this commit saves the error in the `wpdb::$last_error` property. Sets `last_error` with an error message if: * `wpdb::query()` fails for invalid data * `wpdb::process_fields()` fails to process the value(s) for the field(s) where the value could be too long or contain invalid data Sets `last_query` if `wpdb::query()` fails for invalid data. If `__()` is not available, uses non-translated error message to ensure the error is captured. There is no change to wpdb aborting when an error occurs. Adds tests. Props dlt101, mnelson4, dd32, pento, hellofromTonya, davidbaumwald, sergeybiryukov, johnbillion, swissspidy, datainterlock, anandau14, anthonyeden, asif2bd, audrasjb, chaion07, dpegasusm, fpcsjames, galbaras, jdgrimes, justindocanto, kwisatz, liammitchell, lucasw89, lukecarbis, nettsite, nlpro, procodewp, psufan, richardfoley, skunkbad, travisnorthcutt, woodyhayday, zoiec. Fixes #37267. git-svn-id: https://develop.svn.wordpress.org/trunk@52176 602fd350-edb4-49c9-b593-d223f7449a82		2021-11-16 02:57:53 +00:00
..
data	Editor: Add block theme infrastructure	2021-11-08 23:09:53 +00:00
includes	Add Site Editor and PHP changes from Gutenberg 10.1 - 11.9	2021-11-09 02:15:23 +00:00
tests	WPDB: Capture error in `wpdb::$last_error` when insert fails instead of silently failing for invalid data or value too long.	2021-11-16 02:57:53 +00:00
build.xml	Coding Standards: Replace spaced indentation sections of `phpunit.xml.dist`, `multisite.xml`, and `build.xml` with tabs.	2019-01-28 17:20:06 +00:00
multisite.xml	Build/Test Tools: Update PHPUnit configuration for PHPUnit 9.5.10/8.5.21+.	2021-09-26 03:11:18 +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	Code Modernization: Replace `dirname( __FILE__ )` calls with `__DIR__` magic constant.	2020-02-06 06:31:22 +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.