• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

READMEH A D26-Mar-20191.4 KiB5034

cursors_test.hH A D26-Mar-20192.1 KiB6127

dbcreation_test.hH A D26-Mar-20192.2 KiB6222

dr_prop_test.hH A D26-Mar-20191.3 KiB3715

main.cppH A D26-Mar-201911.2 KiB353284

mysqlcursor.cppH A D26-Mar-20194.4 KiB141104

mysqlcursortest_create.sqlH A D26-Mar-2019785 4215

mysqlcursortest_expectedoutputH A D26-Mar-20194.7 KiB129128

parser_test.hH A D26-Mar-20192.1 KiB6941

schema.sqlH A D26-Mar-20191.5 KiB3926

schema_test.hH A D26-Mar-20191.6 KiB5621

sqltestH A D26-Mar-2019611 3017

sqltest_intH A D26-Mar-2019468 2010

tables_test.hH A D26-Mar-20191.3 KiB4822

tables_test_p.hH A D26-Mar-20193.9 KiB10172

tableview_test.hH A D26-Mar-20191.9 KiB6331

README

11. kdbfeaturestest
2-------------
3
4This is a set of tests for the KDb features.
5Every test is driver-independent.
6
7Usage: run 'kdbfeaturestest --help' for usage details.
8
9
102. sqltest
11----------
12
13A script for easier executing 'parser' subtest within the kdbfeaturestest.
14Usage: run './sqltest' without arguments for usage details.
15
16There is also sqltest_int script accepting interactive mode.
17Usage: run './sqltest_int' without arguments for usage details.
18
19
203. Important documents
21----------------------
22KDb Drivers section of the Development wiki pages:
23http://community.kde.org/KDb/Drivers
24
25
264. Information for KDb drivers developers
27-----------------------------------------
28FIXME: update
29
30While you're developing a new driver or plan to improve existing one, you may want to test
31a number of aspects of the KDb framework to see if the behaviour is like expected.
32
33Following tests should be passed (the order is from most simple test to more complicated):
34
35-dbcreation
36-schema
37-tables
38-cursors
39-tableview (note: it is disabled as KDb is largely non-gui for now)
40-parser
41-dr_prop
42
43If a given driver does not pass one of these tests, and you have found that:
44- the problem is apparently on the KDb side (e.g. crash, or improper behaviour),
45- the problem can be solved by extending the KDb API,
46- the documentation is not correct or not clear enough, or
47- whatever like that...
48
49..please contact KDb maintainer Jaroslaw Staniek, staniek @ kde . org, irc://irc.freenode.net #kexi
50