Files
soci/tests
Vadim Zeitlin cbb28ed046 Use CHECK_THAT() in PostgreSQL unit tests
This is simpler than manually using strncmp() or string::find().

Omit one negative test, it's not clear what was it actually testing for.
2025-04-22 17:02:01 +02:00
..
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 17:58:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00
2025-03-04 18:03:53 +01:00

soci/tests

SOCI tests using CATCH testing framework live here.

Currently one test is built for each backend, i.e. there are soci_oracle_test, soci_postgresql_test, soci_sqlite3_test and so on and for ODBC backend there are multiple versions of the test depending on the ODBC driver used. Each of these tests can be run with a single parameter describing the database to use for testing in the backend-specific way as well as any of the standard CATCH command line options.