Documentation Source Text

Check-in [db6bfdf9aa]
Login

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

Overview
Comment:Fix a typo on the testing.html page.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | branch-3.8.10
Files: files | file ages | folders
SHA1: db6bfdf9aa4aa3e95e3847a55d68af6f70f513da
User & Date: drh 2015-05-19 14:05:24.466
Context
2015-05-20
10:51
Update change log and news for the 3.8.10.2 patch release. (check-in: 3db83e693e user: drh tags: branch-3.8.10)
2015-05-19
14:05
Fix a typo on the testing.html page. (check-in: db6bfdf9aa user: drh tags: branch-3.8.10)
2015-05-15
15:56
Improvements to the testing.html document. (check-in: 0b4aaced39 user: drh tags: branch-3.8.10)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/testing.in.
︙︙
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712

<tcl>hd_fragment thoughts1</tcl>
<h3>7.6 Experience with full test coverage</h3>

<p>The developers of SQLite have found that full coverage testing is an
extremely effective method for locating and preventing bugs.
Because every single branch
instruction in SQLite core code is covered by test cases, the developers
can be confident that changes they make in one part of the code
do not have unintended consequences in other parts of the code.
The many new features and performance improvements that have been
added to SQLite in recent years would not have been possible without
the availability full-coverage testing.</p>

<p>Maintaining 100% MC/DC is laborious and time-consuming.
The level of effort needed to maintain full-coverage testing








|








698
699
700
701
702
703
704
705
706
707
708
709
710
711
712

<tcl>hd_fragment thoughts1</tcl>
<h3>7.6 Experience with full test coverage</h3>

<p>The developers of SQLite have found that full coverage testing is an
extremely effective method for locating and preventing bugs.
Because every single branch
instruction in SQLite core code is covered by test cases, the developers
can be confident that changes made in one part of the code
do not have unintended consequences in other parts of the code.
The many new features and performance improvements that have been
added to SQLite in recent years would not have been possible without
the availability full-coverage testing.</p>

<p>Maintaining 100% MC/DC is laborious and time-consuming.
The level of effort needed to maintain full-coverage testing
︙︙