KDb/Tests: Difference between revisions
< KDb
| Line 1: | Line 1: | ||
==Unit tests== | ==Unit tests== | ||
Predicate has complex functionality and should be covered by unit tests. The current test coverage is poor. | Predicate has complex functionality and should be covered by unit tests. | ||
{{Warning|The current unit test coverage in Predicate is poor. Volunteers wanted!}} | |||
===Running unit tests=== | ===Running unit tests=== | ||
Revision as of 15:01, 27 June 2012
Unit tests
Predicate has complex functionality and should be covered by unit tests.
Warning
The current unit test coverage in Predicate is poor. Volunteers wanted!
Running unit tests
$ cd {BUILDDIR}/Predicate/tests
$ ctest --verbose
HOWTOs
Functional tests
Functional test use many parts of the APIs. They can be also used by newcomers to learn how to use Predicate APIs.
$ cd {BUILDDIR}/tests/features
$ less README # read README file
1. Full test for database, tables and data creation for SQLite:
$ ./predicatefeaturestest -t tables sqlite sqlitetest
On success, sqlitetest file will be created and the test says:
main: "tables" test: PASSED
2. Full test for database, tables and data creation for MySQL server:
$ ./predicatefeaturestest -p {mysql_password} -u {mysql_user} -t tables mysql mysqltest
On success, mysqltest server database will be created and the test says:
main: "tables" test: PASSED