Small. Fast. Reliable.
Choose any three.
Choose any three.
|
C API: Testing Interface Operation Codes
(c3ref/c_testctrl_always.html)
SQLITE_TESTCTRL_FIRST, SQLITE_TESTCTRL_PRNG_SAVE, SQLITE_TESTCTRL_PRNG_RESTORE, SQLITE_TESTCTRL_PRNG_RESET, SQLITE_TESTCTRL_FK_NO_ACTION, SQLITE_TESTCTRL_BITVEC_TEST ...
... These values are for testing purposes only.
Applications should not use any of these parameters or the
sqlite3_test_control() interface.
See also lists of
Objects,
Constants, and
Functions.
|
|
C API: Testing Interface
(c3ref/test_control.html)
sqlite3_test_control()
The sqlite3_test_control() interface is used to read out internal
state of SQLite and to inject faults into SQLite for testing
purposes. The first parameter is an operation code that determines
the number, meaning, and operation of all subsequent parameters.
This ...
|
|
C API: Test For Auto-Commit Mode
(c3ref/get_autocommit.html)
sqlite3_get_autocommit()
The sqlite3_get_autocommit() interface returns non-zero or
zero if the given database connection is or is not in autocommit mode,
respectively. Autocommit mode is on by default.
Autocommit mode is disabled by a BEGIN statement.
Autocommit mode is re-enabled ...
|
|
C API: Test To See If The Library Is Threadsafe
(c3ref/threadsafe.html)
sqlite3_threadsafe()
The sqlite3_threadsafe() function returns zero if and only if
SQLite was compiled with mutexing code omitted due to the
SQLITE_THREADSAFE compile-time option being set to 0.
SQLite can be compiled with or without mutexes. When
the SQLITE_THREADSAFE C preprocessor ...
|
|
How SQLite Is Tested
(testing.html)
1. Introduction
The reliability and robustness of SQLite is achieved in part
by thorough and careful testing.
As of version 3.42.0 (2023-05-16),
the SQLite library consists of approximately
155.8 KSLOC of C code.
(KSLOC means thousands of ...
|
|
TH3
(th3.html)
4. Test Coverage
Using one particular subset of the available TH3 test modules (the "cov1"
tests) SQLite obtained
100% branch test coverage and 100% MC/DC as measured
by gcov
on Linux x86 and x86_64 hardware. All releases of SQLite since
version 3 ...
|
|
SQLite Database Speed Comparison
(speed.html)
... These tests are on a relatively small (approximately 14 megabyte) database.
They do not measure how well the database engines scale to larger problems.
Test Environment
The platform used for these tests is a 1.6GHz Athlon with 1GB or ...
|
|
Quality Management
(qmplan.html)
5.3.3. SQL Logic Test
The SQL Logic Tests are a set of test cases designed to show that
SQLite behaves the same as other SQL database engines. These tests
are hosted in a separate code public repository.
Primary location: https://sqlite.org/sqllogictest
Backups ...
|
|
The Use Of assert() In SQLite
(assert.html)
1.2. Different Behaviors According To Build Type
... A functionality testing build is used to validate the source code.
A coverage testing build is used to validate the test suite, to confirm
that the test suite provides 100% MC/DC.
The release build is used to validate the ...
|
|
About SQLite
(about.html)
... SQLite is
very carefully tested prior to every
release and has a reputation for being very reliable.
Most of the SQLite source code is devoted purely to testing and
verification. An automated test suite runs millions and millions of
test ...
|
Page generated by FTS5 in about 127.58 ms.