View source for OpenDBX/Test application

There are two applications for testing the OpenDBX library and their backends available when building the library from source.

== Name ==

These to applications can be found in the "test" sub-directory of the extracted tarball:

 ./test/odbxtest
 ./test/odbxplustest

The first one (odbxtest) uses the C library functions available from libopendbx while the second one (odbxplustest) executes the same statements by using the C++ objects from libopendbxplus.

== Sypnosis ==

 ./test/odbxtest -b <backend or library>
   -h <host or IP or directory> [-p <port>]
   -d <database or file name> -u <user name>
   -w <password> [-r <runs>] [-e]

 ./test/odbxplustest -b <backend or library>
   -h <host or IP or directory> [-p <port>]
   -d <database or file name> -u <user name>
   -w <password> [-r <runs>] [-e]

== Description ==

The applications execute a test suite containing a predefined set of SQL statements against your server. This includes creating a table, inserting rows, performing multiple SELECT, UPDATE and DELETE statements (also within transactions if supported). It also removes the created table and tests for certain error conditions.

== Options ==

; -b <backend> : Name of the database backend (see list of [[OpenDBX/Support|supported backends]]) or path to the backend library (e.g. "./backends/mysql/.libs/libmysqlbackend.so")

; -h <host> : Host name, IP address or directory path to the database file. Look at the [[OpenDBX/Configuration|database specific configuration]] for details

; -p <port> : Port the server is listening to. Usually, this is the port number, some databases also support the port name. Most of the time it's optional and the default port is used by the native database client, but sometimes it's required (like for the Oracle backend)

; -d <database> : Name of the database or database file in the file system

; -u <user> : User name for authentication (not required for sqlite or sqlite3 backends)

; -w <password> : Password for authentication (not required for sqlite or sqlite3 backends)

; -r <runs> : Number of times the test suite is executed (optional)

; -e : Enable encryption to the database server if supported (optional)