1<?xml version="1.0" encoding="UTF-8" standalone="no"?> 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html xmlns="http://www.w3.org/1999/xhtml"> 4 <head> 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> 6 <title>Chapter��46.�� Test Suite</title> 7 <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> 8 <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> 9 <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 10 <link rel="up" href="index.html" title="Berkeley DB Programmer's Reference Guide" /> 11 <link rel="prev" href="changelog_4_8.html" title="Berkeley DB 4.8.30 Change Log" /> 12 <link rel="next" href="test_faq.html" title="Test suite FAQ" /> 13 </head> 14 <body> 15 <div class="navheader"> 16 <table width="100%" summary="Navigation header"> 17 <tr> 18 <th colspan="3" align="center">Chapter��46.�� 19 Test Suite 20 </th> 21 </tr> 22 <tr> 23 <td width="20%" align="left"><a accesskey="p" href="changelog_4_8.html">Prev</a>��</td> 24 <th width="60%" align="center">��</th> 25 <td width="20%" align="right">��<a accesskey="n" href="test_faq.html">Next</a></td> 26 </tr> 27 </table> 28 <hr /> 29 </div> 30 <div class="chapter" lang="en" xml:lang="en"> 31 <div class="titlepage"> 32 <div> 33 <div> 34 <h2 class="title"><a id="test"></a>Chapter��46.�� 35 Test Suite 36 </h2> 37 </div> 38 </div> 39 </div> 40 <div class="toc"> 41 <p> 42 <b>Table of Contents</b> 43 </p> 44 <dl> 45 <dt> 46 <span class="sect1"> 47 <a href="test.html#test_run">Running the test suite</a> 48 </span> 49 </dt> 50 <dt> 51 <span class="sect1"> 52 <a href="test_faq.html">Test suite FAQ</a> 53 </span> 54 </dt> 55 </dl> 56 </div> 57 <div class="sect1" lang="en" xml:lang="en"> 58 <div class="titlepage"> 59 <div> 60 <div> 61 <h2 class="title" style="clear: both"><a id="test_run"></a>Running the test suite</h2> 62 </div> 63 </div> 64 </div> 65 <p>Once you have started tclsh and have loaded the test.tcl source file 66(see <a class="xref" href="build_unix_test.html" title="Running the test suite under UNIX">Running the test suite under UNIX</a> and 67<a class="xref" href="build_win_test.html" title="Running the test suite under Windows">Running the test suite under Windows</a> for more information), 68you are ready to run the test 69suite. At the tclsh prompt, to run the standard test suite, enter the 70following:</p> 71 <pre class="programlisting">% run_std</pre> 72 <p>A more exhaustive version of the test suite runs all the tests several 73more times, testing encryption, replication, and different page sizes. 74After you have a clean run for run_std, you may choose to run this 75lengthier set of tests. At the tclsh prompt, enter:</p> 76 <pre class="programlisting">% run_all</pre> 77 <p>Running the standard tests can take from several hours to a few days to 78complete, depending on your hardware, and running all the tests will 79take at least twice as long. For this reason, the output from these 80commands are redirected to a file in the current directory named 81<code class="filename">ALL.OUT</code>. Periodically, a line will be written to the standard 82output, indicating what test is being run. When the test suite has 83finished, a final message will be written indicating the test suite has 84completed successfully or that it has failed. If the run failed, you 85should review the <code class="filename">ALL.OUT</code> file to determine which tests failed. 86Errors will appear in that file as output lines, beginning with the 87string "FAIL".</p> 88 <p>Tests are run in the directory <code class="filename">TESTDIR</code>, by default. However, 89the test files are often large, and you should use a filesystem with at 90least several hundred megabytes of free space. To use a different 91directory for the test directory, edit the file include.tcl in your 92build directory, and change the following line to a more appropriate 93value for your system:</p> 94 <pre class="programlisting">set testdir ./TESTDIR</pre> 95 <p>For example, you might change it to the following:</p> 96 <pre class="programlisting">set testdir /var/tmp/db.test</pre> 97 <p>Alternatively, you can create a symbolic link named TESTDIR in your 98build directory to an appropriate location for running the tests. 99Regardless of where you run the tests, the TESTDIR directory should be 100on a local filesystem. Using a remote filesystem (for example, an NFS 101mounted filesystem) will almost certainly cause spurious test 102failures.</p> 103 </div> 104 </div> 105 <div class="navfooter"> 106 <hr /> 107 <table width="100%" summary="Navigation footer"> 108 <tr> 109 <td width="40%" align="left"><a accesskey="p" href="changelog_4_8.html">Prev</a>��</td> 110 <td width="20%" align="center">��</td> 111 <td width="40%" align="right">��<a accesskey="n" href="test_faq.html">Next</a></td> 112 </tr> 113 <tr> 114 <td width="40%" align="left" valign="top">Berkeley DB 4.8.30 Change Log��</td> 115 <td width="20%" align="center"> 116 <a accesskey="h" href="index.html">Home</a> 117 </td> 118 <td width="40%" align="right" valign="top">��Test suite FAQ</td> 119 </tr> 120 </table> 121 </div> 122 </body> 123</html> 124