Documentation Source Text

Check-in [c345c5933b]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Update the testing document to indicate that the unix VFS now has 100% branch test coverage.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: c345c5933b2b774b06d60b6f42a482791edde2f5
User & Date: drh 2015-12-02 20:59:01
Context
2015-12-03
22:05
Merge the AUTOINCREMENT typo fix from the 3.9 branch. check-in: 3dec493cba user: drh tags: trunk
2015-12-02
20:59
Update the testing document to indicate that the unix VFS now has 100% branch test coverage. check-in: c345c5933b user: drh tags: trunk
2015-11-30
19:36
Add information about the sqlite3_index_info.colUsed field. check-in: 43d4cb5785 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/testing.in.

461
462
463
464
465
466
467

468
469
470
471
472
473
474
475

476
477
478
479
480
481
482
quickly.  SQLite is designed to never leak memory, even after
an exception such as an OOM error or disk I/O error.  The test
harnesses are zealous to enforce this.</p>

<tcl>hd_fragment coverage {test coverage}</tcl>
<h2>7.0 Test Coverage</h2>


<p>The SQLite core has 100% branch test coverage under [TH3] in
its default configuration as measured by
[http://gcc.gnu.org/onlinedocs/gcc/Gcov.html | gcov].</p>

<p>The "SQLite core" in the previous paragraph excludes the
operating-system dependent [VFS] backends, since it is
not possible to write cross-platform tests for those modules.  Extensions
such as FTS3 and RTree are also excluded from the analysis.</p>


<tcl>hd_fragment stmtvbr</tcl>
<h3>7.1 Statement versus branch coverage</h3>

<p>There are many ways to measure test coverage.  The most popular
metric is "statement coverage".  When you hear someone say that their
program as "XX% test coverage" without further explanation, they usually







>
|

|
<
<
<
<
|
>







461
462
463
464
465
466
467
468
469
470
471




472
473
474
475
476
477
478
479
480
quickly.  SQLite is designed to never leak memory, even after
an exception such as an OOM error or disk I/O error.  The test
harnesses are zealous to enforce this.</p>

<tcl>hd_fragment coverage {test coverage}</tcl>
<h2>7.0 Test Coverage</h2>

<p>The SQLite core, including the unix [VFS],
has 100% branch test coverage under [TH3] in
its default configuration as measured by
[http://gcc.gnu.org/onlinedocs/gcc/Gcov.html | gcov].




Extensions such as FTS3 and RTree are excluded from this
analysis.</p>

<tcl>hd_fragment stmtvbr</tcl>
<h3>7.1 Statement versus branch coverage</h3>

<p>There are many ways to measure test coverage.  The most popular
metric is "statement coverage".  When you hear someone say that their
program as "XX% test coverage" without further explanation, they usually