lacak 382cd9483c Adds test for Firebird's EXECUTE BLOCK RETURNS statement, which returns resultset. Test correct detection of StatementType. Mantis #0022972 13 years ago
..
Makefile 1b3fd997fc + Regenerate all Makefiles's after adding x86_64 netbsd target 13 years ago
Makefile.fpc 4c7f9238c7 * SQL parser 15 years ago
README.txt 6776c54357 * patch from Reinier: More details on setting up test database, ignoring tests for certain databases.... mantis #22970 13 years ago
XMLXSDExportTest.lpi b11276b34f * Patch from Graeme to reduce dependencies (consolerunner is now in FCL) 13 years ago
XMLXSDExportTest.lpr f0bbea9319 * Tester for XSD export 14 years ago
bufdatasettoolsunit.pas a1b3e79554 * improvements to bufdataset testsuite specially for ftmemo and ftblob. 13 years ago
database.ini.txt 91f1a8736c + Added experimental support for Sybase ASE connector in database tests 13 years ago
dbfexporttest.lpi b11276b34f * Patch from Graeme to reduce dependencies (consolerunner is now in FCL) 13 years ago
dbfexporttest.lpr 3cc6ac9e3b * Testcase for DBF export 14 years ago
dbfexporttestcase1.pas 6ed8641937 * patch from BigChimp, fixing dbf related testing of output, from 14 years ago
dbftoolsunit.pas f016c79d7a * Patch from Luiz Americo to fix a double pathdelim in filename, bug #16737 15 years ago
dbtestframework.pas f496994f46 * Use consoletestrunner from fcl-unit. Old output available through --legacy or -g 13 years ago
dbtestframework_gui.lpi 3f803013a3 * Applied patch from #22899 13 years ago
dbtestframework_gui.lpr 3f803013a3 * Applied patch from #22899 13 years ago
memdstoolsunit.pas 5b8dd4c004 * move fcl sources to separate packages 18 years ago
sdfdstoolsunit.pas 3f803013a3 * Applied patch from #22899 13 years ago
sqldbtoolsunit.pas 91f1a8736c + Added experimental support for Sybase ASE connector in database tests 13 years ago
tcgensql.pas 6df8ec1ce8 * Added tests for Grant/Revoke, fixed some bugs on the way 15 years ago
tcparser.pas 672d7f6b63 * Implemented AS for table aliases 13 years ago
tcsdfdata.pp 3f803013a3 * Applied patch from #22899 13 years ago
tcsqlscanner.pas 6df8ec1ce8 * Added tests for Grant/Revoke, fixed some bugs on the way 15 years ago
test.json 9135ece182 * Example for JSON dataset 13 years ago
testbasics.pas 872409d293 * Forgot to apply patch from #21905 in trunk 13 years ago
testbufdatasetstreams.pas ec67f10680 * Fixed CreateDataset when TBufDataset.Filename is set 13 years ago
testdatasources.pas 1da7000192 * Added test for CalcLookupValue 17 years ago
testdbbasics.pas a320db479e * applied BOF patch + test from Lacak2. Mantis #22377 13 years ago
testdddiff.pp c2dc42bb89 * test for Data dictionary diff mechanism 17 years ago
testfieldtypes.pas 382cd9483c Adds test for Firebird's EXECUTE BLOCK RETURNS statement, which returns resultset. Test correct detection of StatementType. Mantis #0022972 13 years ago
testjsondataset.pp 310e8e0b9c * Removed resource added by lazarus 13 years ago
testspecifictbufdataset.pas c02351da63 * Implemented autoincremental fields for TBufDataset 13 years ago
testsqlfiles.lpi b11276b34f * Patch from Graeme to reduce dependencies (consolerunner is now in FCL) 13 years ago
testsqlfiles.lpr 4c7f9238c7 * SQL parser 15 years ago
testsqlscanner.lpi b11276b34f * Patch from Graeme to reduce dependencies (consolerunner is now in FCL) 13 years ago
testsqlscanner.lpr 4c7f9238c7 * SQL parser 15 years ago
testsqlscript.pas cc0c2d6467 * SqlScript committed 17 years ago
toolsunit.pas 3f803013a3 * Applied patch from #22899 13 years ago
xmlxsdexporttestcase1.pas dc0be272a0 * Better test case from Reinier, Bug ID #19987 14 years ago

README.txt

This directory contains a framework to test several TDataset descendents.
A lot of these tests are only applicable for SQL databases, but there are several tests that also apply to other objects, such as TBufDataset.

The framework is based on the fpcunit unit test system. The tests can be
executed using any fpcunit testrunner. For example the console and graphical
fpcunit test runners from Lazarus.
Simply add the test* units in this directory to the uses statement of the
test runner and all tests will get registered and executed.

A simple test runner (dbtestframework.pas) which generates XML output is
included in this directory.

DBTestframework architecture
============================
To test a TDataset descendent, a 'connector' is needed to test the database.
To add a new connector, create a new *toolsunit.pas file, then add it to
the uses section in 'dbtestframework.pas'. Several connectors are available
in the '*toolsunit.pas' files.

The connector must inherit from TDBConnector in toolsunit.pas.
The connector implements two different kinds of datasets:
- a dataset with as many different kinds of fields as possible (see the *FieldDataSets subroutines).
- a dataset with only a few fields (ID and NAME), but a lot (well, MaxDataset) of different records (see the *NDataSets subroutines)

CreateNDatasets and CreateFieldDataset should be implemented to set up data stores (e.g. database tables) and fill these stores with test data for the respective datasets.
The corresponding Drop*Dataset procedures must drop the tables/delete the data.

GetNDataset and GetFieldsDataset should return the relevant dataset in closed state so the tests can open them and work with them.
They call InternalGetNDataset and InternalGetFieldDataset which should be implemented in all descendents and returns the relevant dataset, closed, with all data.

Toolsunit.pas defines some variables for use, e.g. testValuesCount is the number of records/test values in the FieldDataset dataset; MaxDataset is the same for NDataset.
See e.g. the SQLDBToolsUnit for the implementation for SQL Databases.

Tests
=====
In your test units, you can specify that you only want to run for certain groups/connectors.
E.g. this example to only run for Bufdataset tests:
TTestSpecificTBufDataset = class(TTestCase)
...
initialization
if uppercase(dbconnectorname)='BUFDATASET' then
begin
RegisterTestDecorator(TDBBasicsTestSetup, TTestSpecificTBufDataset);
end;

In your individual tests, you can indicate you want to run tests only in certain cases, e.g. for certain SQLDB databases:
if not(SQLDbType in [interbase]) then Ignore(STestNotApplicable);

Setting up your database
========================
Some tests are file based (e.g. those for bufdataset); others by their nature need databases (e.g. a Firebird SQLDB test).
File-based tests will generally write to the current/test directory, a subdirectory or a temp file.

For SQLDB database servers, please make sure you have a username/password and a database set up that the test suite can use and abuse.
The database can be empty: the test suite will create and delete tables etc. in this database as needed.

Specifying databases, connector names
=====================================
Which connector is currently used is dependent on the 'database.ini'
configuration file. Also some settings which are connector-dependent can be set
in that file. See 'database.ini.txt' for an example.

The connector names to be used are derived from the connector classes.

For example, the SQL RDBMS connector defined in sqldbtoolsunit:
- it has this class definition
TSQLDBConnector = class(TDBConnector)
- its name in database.ini is sqldb
- incidentally, in databases.ini, more parameter such as
connectorparams=postgresql (which specify db type) are needed
The parameters use depend on the connector type (sql,...)

If you specify the wrong (or no) name (or don't have database.ini), you will get an exception in your test runner:
Unknown db connector specified

Joost van der Sluis (30-12-2006),
amended by Reinier Olislagers (2012)