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

..07-May-2022-

.gitignoreH A D26-Mar-201910 21

READMEH A D26-Mar-20191.6 KiB5940

cursors_test.hH A D26-Mar-20192 KiB6127

dbcreation_test.hH A D26-Mar-20192.2 KiB637

dr_prop_test.hH A D26-Mar-20191.5 KiB4115

main.cppH A D26-Mar-20199.6 KiB284214

mysqlcursor.cppH A D26-Mar-20193.5 KiB125107

mysqlcursortest_create.sqlH A D26-Mar-2019785 4215

mysqlcursortest_expectedoutputH A D26-Mar-20194.7 KiB129128

parser_test.hH A D26-Mar-20191.8 KiB6233

schema.sqlH A D26-Mar-20191.5 KiB3926

schema_test.hH A D26-Mar-20191.6 KiB5621

sqltestH A D26-Mar-2019586 3017

sqltest_intH A D26-Mar-2019426 2011

tableview_test.hH A D26-Mar-20192 KiB6733

README

1All tests should be run from {BUILDDIR}/kexi/tests/newapi/ directory because binaries
2are not installed during build.
3
41. kexidbtest
5-------------
6
7This is a set of tests for the new, common KexiDB API.
8Every test is driver-independent.
9
10Usage: run 'kexidbtest --help' for usage details.
11
12
132. sqltest
14----------
15
16Script for easier executing 'parser' subtest within kexidbtest.
17Usage: run 'path/to/sqltest' without arguments for usage details.
18
19There is also sqltest_int script accepting interactive mode, asking for statement in a loop.
20Usage: run 'path/to/sqltest_int' without arguments for usage details.
21
22
233. Important documents
24----------------------
25* API Documentation in html
26  http://api.kde.org/bundled-apps-api/calligra-apidocs/libs/db/html/index.html
27
28* KexiDB section on the wiki
29  https://community.kde.org/Kexi/KexiDB
30
31
32
334. Information for KexiDB drivers developers
34--------------------------------------------
35
36While you're developing new driver or improving existing one,
37you may want to test a number of aspects to see if the behaviour
38looks like expected.
39
40Following tests should be passed (the order is from most simple
41test to more complicated):
42
43-dbcreation
44-schema
45-tables
46-cursors
47-tableview
48-parser
49-dr_prop
50
51If the given driver does not pass one of these tests, and you have found:
52- that the problem is at the KexiDB library side (e.g. crash, or improper
53behaviour), or
54- that the problem can be solved by extending KexiDB API, or
55- that the documentation is not correct or not enough detailed, or
56- whatever like that,
57
58..please contact authors: https://community.kde.org/Kexi/Contact
59