Differences

This shows you the differences between two versions of the page.

--- project:unittests [2025/07/21 03:36] – mnewnham
+++ project:unittests [2025/08/01 00:37] (current) – mnewnham
@@ Line 3: / Line 3: @@
 Unit testing can be done using PHPUnit testing. Testing can be done against any database that is available that you have admin rights on. The test creates tables, populates them with small amounts of data and drops them.
-===== Setup ====
+===== Setup =====
-Configuration information for the tests is held in a configuration file adodb-unittest.ini. The file can be located anywhere in the PHP include path. The configuration is based on the driver name.
+Configuration information for the tests is held in a configuration file adodb-unittest.ini. The file can be located anywhere in the PHP include path.
+==== ADOdb Section ====
+If the ADOdb section is defined, and the item directory is set, the the tests can be run against an ADOdb installation set locally. This is useful if ADOdb is embedded into a different application
+<code>
+[ADOdb]
+directory=/opt/some/local/ADOdb/installation
+</code>
+If the section is not defined, it assumes that the ADOdb installation is the parent directory of the unit test
+<code>
+/opt/ADOdb
+/opt/ADOdb/unittest
+</code>
+==== Blob Section ====
+This section must be defined, either with the path name to a binary file, such as a jpeg file that can be used for read-write testing. If set to false, all blob tests are skipped.
+<code>
+[blob]
+testBlob=c:/temp/someJpeg.jpg
+</code>
+==== Driver Section ====
+The driver configuration is based on the driver name.
 <code>
@@ Line 15: / Line 41: @@
 debug=0
 parameters=
+active=1
 </code>
@@ Line 24: / Line 51: @@
 |debug|Sets the debug mode|
 |parameters|To set parameters normally set by ''setConnectionParameter()'', create a string in format **key=value;** Note that the parameters cannot be defined as constants, you must use the numeric or string equivalents|
+|active|If a run-time parameter of the driver is not passed of the PHPunit version > 9, then the test is run against the first driver where the active flag is set to true|
-===== Test Execution =====
+==== Meta Section ====
+Unless explicitly enabled, the test to create new database using the //**createDatabase**// method is skipped as it requires CREATE DATABASE privilege on the DBMS. To enable this test, set the following section:
+<code>[meta]
+skipDbCreation=0
+</code>
+==== Caching Section ====
+Unless explicitly enabled, cache functions such as //**CacheExecute()**// are skipped. Tests only currently support Filesystem based caching. To activate this, add the following section to adodb-unittest.ini:
+<code>
+[caching]
+cacheMethod=1
+cacheDir=c:/dev/cache
+</code>
+To disable cache tests while leaving the section in place, ''set cacheMethod=0''
+==== Globals Section ====
+To test some date functions, the local timezone must be equal to the server timezone. To change the timezone temporarily for the test, set the following gloval parameter in adodb-unittest.ini. This should exactly match the format in php.ini.
+<code>
+[globals]
+date.timezone = 'America/Denver'
+</code>
+Any parameter saved into the **[globals]** section will be set using ini_set()
+===== Test Execution =====
+==== PHPUnit 9 or lower ====
 <code>
 phpunit unittest --bootstrap unittest/dbconnector.php <driver>
@@ Line 32: / Line 89: @@
 Where the <driver> name represents the ADOdb driver to use. For use of PDO drivers use the format pdo-<driver>. The driver name **__must__** follow the bootstrap file name
+==== PHPUnit 10 or higher ====
+<code>
+phpunit unittest --bootstrap unittest/dbconnector.php
+</code>
+The driver to test must have the **active** flag defined in the driver section