Fix the Jenkins link, add a section on static testing

2 files changed, 40 insertions, 26 deletions

diff --git a/src/docs/spell.ok b/src/docs/spell.ok
index 0fbe636fb84..e76c82eca86 100644
--- a/src/docs/spell.ok
+++ b/src/docs/spell.ok
@@ -9,8 +9,8 @@ ao
 api
 apiflags
 APIs
-ar
 aR
+ar
 archiver
 arg
 Atomicity
@@ -55,6 +55,8 @@ configurign
 conn
 const
 control's
+Coverity
+Coverity's
 cpp
 CPPFLAGS
 crashless
@@ -63,14 +65,14 @@ cv
 dataitem
 dataN
 datasets
-datastore
 Datastore
+datastore
+DB's
 dbc
 DbCursor
 DbEnv
 dbm
 DbMultiple
-DB's
 dbt
 DBTs
 decl
@@ -90,8 +92,8 @@ dp
 ds
 dsrc
 dsync
-dt
 dT
+dt
 dumpfile
 dup
 dups
@@ -122,6 +124,7 @@ filesystem
 filesystems
 fillfactor
 firstname
+FlexeLint
 fnv
 forw
 fput
@@ -130,14 +133,15 @@ FreeBSD's
 freelist
 fsync
 Gawlick
-gcc
 GCC
+gcc
 gdbm
 getopt
 getter
 gid
-github
+Gimpel
 GitHub
+github
 gnuplot
 Google
 Google's
@@ -188,8 +192,8 @@ lookup
 lookups
 lrtf
 LSB
-lsm
 LSM
+lsm
 lsn
 lt
 mailto
@@ -221,8 +225,8 @@ msg
 msgs
 multi
 multiprocess
-multithreaded
 Multithreaded
+multithreaded
 multithreading
 multiversion
 mutex
@@ -243,8 +247,8 @@ noflush
 nolocking
 nommap
 nop
-nosql
 NoSQL
+nosql
 nosync
 NOTFOUND
 notgranted
@@ -252,8 +256,8 @@ notyet
 nowait
 nul
 num
-numa
 NUMA
+numa
 objectsin
 ol
 oltp
@@ -309,8 +313,8 @@ selectable
 seqname
 serializable
 Seward's
-sHq
 sHQ
+sHq
 SiS
 spinlock
 spinlocks
@@ -371,10 +375,10 @@ versa
 vm
 Vv
 whitespace
-wiredtiger
 WiredTiger
-WiredTigerCheckpoint
+wiredtiger
 WiredTiger's
+WiredTigerCheckpoint
 WiredTigerTestCase
 workQ
 writelock
diff --git a/src/docs/testing.dox b/src/docs/testing.dox
index 879d86fb502..d375a457f59 100644
--- a/src/docs/testing.dox
+++ b/src/docs/testing.dox
@@ -1,28 +1,24 @@
 /*!
-@page testing How WiredTiger is Tested
+@page testing WiredTiger testing
 
-WiredTiger uses several different tools for testing WiredTiger - using
-different tools allows us to effectively test different aspects of reliability.
-The testing can be broken into the following categories:
+WiredTiger uses several different tools for testing WiredTiger, allowing
+effective testing of different aspects of reliability.  The testing can
+be separated into the following categories:
 
 - Functionality coverage
-
 - Bug regression testing
-
 - Cross platform testing
-
 - Multi-threading testing
-
 - Stress testing
-
+- Static analysis
 - Performance testing
 
 The above test dimensions are discussed in more detail below.
 
-Our tests are automatically run using the Jenkins (http://www.jenkins.org/)
-continuous integration testing framework. This allows us to be confident
-that we maintain support for all platforms, and aren't introducing performance
-regressions over time.
+Most WiredTiger testing is done automatically using the <a
+href="http://jenkins-ci.org/">Jenkins</a> continuous integration testing
+framework. This allows us to be confident we maintain support for all
+platforms, and don't introduce performance regressions.
 
 @section test_suite Unit Test Suite
 
@@ -148,4 +144,18 @@ several days!)
 We test performance using the wtperf tool, running a variety of configurations
 on every push, and tracking any performance regressions.
 
+@section testing_static Static analysis
+
+Static analysis for WiredTiger is done using two tools:
+
+- The <a href="https://www.coverity.com/">Coverity,
+Inc.</a>software analysis tool; current results and historic defect
+reports are available at <a
+href="https://scan.coverity.com/projects/1018">Coverity's WiredTiger
+page</a>.
+
+- The Gimpel Software <a
+href="http://www.gimpel.com/html/flex.htm">FlexeLint</a> implementation
+of the UNIX lint tool.
+
  */