1<!--$Id: run.so,v 10.49 2007/07/27 14:19:26 bostic Exp $-->
2<!--Copyright (c) 1997,2008 Oracle.  All rights reserved.-->
3<!--See the file LICENSE for redistribution information.-->
4<html>
5<head>
6<title>Berkeley DB Reference Guide: Running the test suite</title>
7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
9</head>
10<body bgcolor=white>
11<a name="2"><!--meow--></a>
12<table width="100%"><tr valign=top>
13<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Test Suite</dl></b></td>
14<td align=right><a href="/upgrade.4.7/disk.html"><img src="/images/prev.gif" alt="Prev"></a><a href="/toc.html"><img src="/images/ref.gif" alt="Ref"></a><a href="/test/faq.html"><img src="/images/next.gif" alt="Next"></a>
15</td></tr></table>
16<p align=center><b>Running the test suite</b></p>
17<p>Once you have started tclsh and have loaded the test.tcl source file
18(see <a href="/ref/build_unix/test.html">Running the test suite under
19UNIX</a> and <a href="/ref/build_win/test.html">Running the test suite
20under Windows</a> for more information), you are ready to run the test
21suite.  At the tclsh prompt, to run the standard test suite, enter the
22following:</p>
23<blockquote><pre>% run_std</pre></blockquote>
24<p>A more exhaustive version of the test suite runs all the tests several
25more times, testing encryption, replication, and different page sizes.
26After you have a clean run for run_std, you may choose to run this
27lengthier set of tests.  At the tclsh prompt, enter:</p>
28<blockquote><pre>% run_all</pre></blockquote>
29<p>Running the standard tests can take from several hours to a few days to
30complete, depending on your hardware, and running all the tests will
31take at least twice as long.  For this reason, the output from these
32commands are redirected to a file in the current directory named
33<b>ALL.OUT</b>.  Periodically, a line will be written to the standard
34output, indicating what test is being run.  When the test suite has
35finished, a final message will be written indicating the test suite has
36completed successfully or that it has failed.  If the run failed, you
37should review the <b>ALL.OUT</b> file to determine which tests failed.
38Errors will appear in that file as output lines, beginning with the
39string "FAIL".</p>
40<p>Tests are run in the directory <b>TESTDIR</b>, by default.  However,
41the test files are often large, and you should use a filesystem with at
42least several hundred megabytes of free space.  To use a different
43directory for the test directory, edit the file include.tcl in your
44build directory, and change the following line to a more appropriate
45value for your system:</p>
46<blockquote><pre>set testdir /TESTDIR</pre></blockquote>
47<p>For example, you might change it to the following:</p>
48<blockquote><pre>set testdir /var/tmp/db.test</pre></blockquote>
49<p>Alternatively, you can create a symbolic link named TESTDIR in your
50build directory to an appropriate location for running the tests.
51Regardless of where you run the tests, the TESTDIR directory should be
52on a local filesystem.  Using a remote filesystem (for example, an NFS
53mounted filesystem) will almost certainly cause spurious test
54failures.</p>
55<table width="100%"><tr><td><br></td><td align=right><a href="/upgrade.4.7/disk.html"><img src="/images/prev.gif" alt="Prev"></a><a href="/toc.html"><img src="/images/ref.gif" alt="Ref"></a><a href="/test/faq.html"><img src="/images/next.gif" alt="Next"></a>
56</td></tr></table>
57<p><font size=1>Copyright (c) 1996,2008 Oracle.  All rights reserved.</font>
58</body>
59</html>
60