003 File Manager
Current Path:
/usr/local/share/doc/db5/installation
usr
/
local
/
share
/
doc
/
db5
/
installation
/
📁
..
📄
BDB_Installation.pdf
(942.78 KB)
📄
arch_bigpic.gif
(2.53 KB)
📄
arch_smallpic.gif
(1.58 KB)
📄
build_android_config.html
(4.9 KB)
📄
build_android_intro.html
(12.27 KB)
📄
build_android_jdbc.html
(15.97 KB)
📄
build_unix.html
(12.24 KB)
📄
build_unix_aix.html
(7.99 KB)
📄
build_unix_conf.html
(27.32 KB)
📄
build_unix_db_nosync.html
(3.29 KB)
📄
build_unix_encrypt.html
(3.55 KB)
📄
build_unix_flags.html
(5.23 KB)
📄
build_unix_freebsd.html
(3.57 KB)
📄
build_unix_install.html
(6.52 KB)
📄
build_unix_iphone.html
(4.4 KB)
📄
build_unix_irix.html
(3.03 KB)
📄
build_unix_linux.html
(3.9 KB)
📄
build_unix_macosx.html
(4.55 KB)
📄
build_unix_notes.html
(12.13 KB)
📄
build_unix_qnx.html
(6.7 KB)
📄
build_unix_sco.html
(2.84 KB)
📄
build_unix_shlib.html
(8.34 KB)
📄
build_unix_small.html
(9.67 KB)
📄
build_unix_solaris.html
(8.4 KB)
📄
build_unix_sql.html
(29.97 KB)
📄
build_unix_stacksize.html
(2.98 KB)
📄
build_unix_sunos.html
(3.29 KB)
📄
build_unix_test.html
(5.94 KB)
📄
build_vxworks.html
(6.73 KB)
📄
build_vxworks_faq.html
(11.98 KB)
📄
build_vxworks_notes.html
(6.67 KB)
📄
build_win.html
(15.88 KB)
📄
build_win_csharp.html
(5.09 KB)
📄
build_win_faq.html
(7.65 KB)
📄
build_win_java.html
(5.43 KB)
📄
build_win_notes.html
(5.45 KB)
📄
build_win_small.html
(4.76 KB)
📄
build_win_sql.html
(24.89 KB)
📄
build_win_tcl.html
(6.4 KB)
📄
build_win_test.html
(9.53 KB)
📄
build_wince.html
(15.36 KB)
📄
build_wince_faq.html
(6.56 KB)
📄
build_wince_notes.html
(4.77 KB)
📄
ch01s02.html
(5.78 KB)
📄
changelog_4_8.html
(52.46 KB)
📄
changelog_5_0.html
(44.98 KB)
📄
changelog_5_1.html
(37.5 KB)
📄
changelog_5_2.html
(37.49 KB)
📄
changelog_5_3.html
(33.8 KB)
📄
cross_compile_unix.html
(5.35 KB)
📄
debug.html
(8.44 KB)
📄
debug_compile.html
(4.67 KB)
📄
debug_printlog.html
(20.75 KB)
📄
debug_runtime.html
(4.67 KB)
📄
gettingStarted.css
(1.13 KB)
📄
index.html
(64.07 KB)
📄
install.html
(16.79 KB)
📄
install_multiple.html
(5.19 KB)
📄
introduction.html
(6.29 KB)
📄
moreinfo.html
(7 KB)
📄
preface.html
(4.28 KB)
📄
test.html
(9.25 KB)
📄
test_faq.html
(2.75 KB)
📄
upgrade_11gr2_51_dpl_recompile.html
(3.14 KB)
📄
upgrade_11gr2_51_mod_db4_unsupp.html
(2.78 KB)
📄
upgrade_11gr2_51_sqlite_ver.html
(2.95 KB)
📄
upgrade_11gr2_51_src_reorg.html
(3.04 KB)
📄
upgrade_11gr2_52_bit_cmp_win.html
(3.18 KB)
📄
upgrade_11gr2_52_dyn_env.html
(7.17 KB)
📄
upgrade_11gr2_52_excl_txn_sql.html
(3.21 KB)
📄
upgrade_11gr2_52_grp_mbr.html
(13.25 KB)
📄
upgrade_11gr2_52_heap.html
(5.54 KB)
📄
upgrade_11gr2_52_hot_backup.html
(3.41 KB)
📄
upgrade_11gr2_52_mvcc_sql.html
(4.19 KB)
📄
upgrade_11gr2_52_rep_2site_strict.html
(3.22 KB)
📄
upgrade_11gr2_52_rep_dbt_readonly.html
(3.84 KB)
📄
upgrade_11gr2_52_rep_sql.html
(5.21 KB)
📄
upgrade_11gr2_52_repmgr_channels.html
(5.35 KB)
📄
upgrade_11gr2_52_seq_sql.html
(4.87 KB)
📄
upgrade_11gr2_52_sqlite_ver.html
(3.16 KB)
📄
upgrade_11gr2_52_xa.html
(6.11 KB)
📄
upgrade_11gr2_53_build_windows.html
(3.23 KB)
📄
upgrade_11gr2_53_conn_status.html
(5.19 KB)
📄
upgrade_11gr2_53_excl.html
(4.33 KB)
📄
upgrade_11gr2_53_heap_regionsize.html
(4.04 KB)
📄
upgrade_11gr2_53_hotbackup.html
(7.97 KB)
📄
upgrade_11gr2_53_jdbc.html
(2.94 KB)
📄
upgrade_11gr2_53_meta_dir.html
(4.32 KB)
📄
upgrade_11gr2_53_sql_build.html
(3.41 KB)
📄
upgrade_11gr2_53_sql_pragma.html
(4.23 KB)
📄
upgrade_11gr2_53_sql_rep.html
(4.93 KB)
📄
upgrade_11gr2_53_xa_mvcc.html
(3.23 KB)
📄
upgrade_11gr2_autoinit.html
(3.23 KB)
📄
upgrade_11gr2_dbsqlcodegen.html
(3.01 KB)
📄
upgrade_11gr2_remsupp.html
(2.95 KB)
📄
upgrade_11gr2_repmgr.html
(3.93 KB)
📄
upgrade_11gr2_toc.html
(5.68 KB)
📄
upgrade_4_8_disk.html
(3.16 KB)
📄
upgrade_4_8_dpl.html
(4.1 KB)
📄
upgrade_4_8_fcntl.html
(2.96 KB)
📄
upgrade_4_8_mpool.html
(3.77 KB)
📄
upgrade_4_8_toc.html
(9.92 KB)
📄
upgrade_51_toc.html
(9.31 KB)
📄
upgrade_52_toc.html
(14.82 KB)
📄
upgrade_53_toc.html
(12.24 KB)
📄
win_additional_options.html
(5.46 KB)
📄
win_build64.html
(4.71 KB)
📄
win_build_cxx.html
(2.58 KB)
📄
win_build_cygwin.html
(2.73 KB)
📄
win_build_dist_dll.html
(4.28 KB)
📄
win_build_stl.html
(3.3 KB)
Editing: test.html
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>Chapter 14. Test Suite</title> <link rel="stylesheet" href="gettingStarted.css" type="text/css" /> <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" /> <link rel="start" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="up" href="index.html" title="Berkeley DB Installation and Build Guide" /> <link rel="prev" href="changelog_4_8.html" title="Berkeley DB 4.8.28 Change Log" /> <link rel="next" href="test_faq.html" title="Test suite FAQ" /> </head> <body> <div xmlns="" class="navheader"> <div class="libver"> <p>Library Version 11.2.5.3</p> </div> <table width="100%" summary="Navigation header"> <tr> <th colspan="3" align="center">Chapter 14. Test Suite </th> </tr> <tr> <td width="20%" align="left"><a accesskey="p" href="changelog_4_8.html">Prev</a> </td> <th width="60%" align="center"> </th> <td width="20%" align="right"> <a accesskey="n" href="test_faq.html">Next</a></td> </tr> </table> <hr /> </div> <div class="chapter" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h2 class="title"><a id="test"></a>Chapter 14. Test Suite </h2> </div> </div> </div> <div class="toc"> <p> <b>Table of Contents</b> </p> <dl> <dt> <span class="sect1"> <a href="test.html#test_run">Running the test suite</a> </span> </dt> <dd> <dl> <dt> <span class="sect2"> <a href="test.html#idp1298736">Running SQL Test Suite on Unix</a> </span> </dt> <dt> <span class="sect2"> <a href="test.html#idp1289848">Running SQL Test Suite on Windows</a> </span> </dt> </dl> </dd> <dt> <span class="sect1"> <a href="test_faq.html">Test suite FAQ</a> </span> </dt> </dl> </div> <div class="sect1" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h2 class="title" style="clear: both"><a id="test_run"></a>Running the test suite</h2> </div> </div> </div> <div class="toc"> <dl> <dt> <span class="sect2"> <a href="test.html#idp1298736">Running SQL Test Suite on Unix</a> </span> </dt> <dt> <span class="sect2"> <a href="test.html#idp1289848">Running SQL Test Suite on Windows</a> </span> </dt> </dl> </div> <p>Once you have started tclsh and have loaded the test.tcl source file (see <a class="xref" href="build_unix_test.html" title="Running the test suite under UNIX">Running the test suite under UNIX</a> and <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), you are ready to run the test suite. At the tclsh prompt, to run the standard test suite, enter the following:</p> <pre class="programlisting">% run_std</pre> <p>A more exhaustive version of the test suite runs all the tests several more times, testing encryption, replication, and different page sizes. After you have a clean run for run_std, you may choose to run this lengthier set of tests. At the tclsh prompt, enter:</p> <pre class="programlisting">% run_all</pre> <p>Running the standard tests can take from several hours to a few days to complete, depending on your hardware, and running all the tests will take at least twice as long. For this reason, the output from these commands are redirected to a file in the current directory named <code class="filename">ALL.OUT</code>. Periodically, a line will be written to the standard output, indicating what test is being run. When the test suite has finished, a final message will be written indicating the test suite has completed successfully or that it has failed. If the run failed, you should review the <code class="filename">ALL.OUT</code> file to determine which tests failed. Errors will appear in that file as output lines, beginning with the string "FAIL".</p> <p>Tests are run in the directory <code class="filename">TESTDIR</code>, by default. However, the test files are often large, and you should use a filesystem with at least several hundred megabytes of free space. To use a different directory for the test directory, edit the file include.tcl in your build directory, and change the following line to a more appropriate value for your system:</p> <pre class="programlisting">set testdir ./TESTDIR</pre> <p>For example, you might change it to the following:</p> <pre class="programlisting">set testdir /var/tmp/db.test</pre> <p>Alternatively, you can create a symbolic link named TESTDIR in your build directory to an appropriate location for running the tests. Regardless of where you run the tests, the TESTDIR directory should be on a local filesystem. Using a remote filesystem (for example, an NFS mounted filesystem) will almost certainly cause spurious test failures.</p> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h3 class="title"><a id="idp1298736"></a>Running SQL Test Suite on Unix</h3> </div> </div> </div> <p> Once the test suite is built (see <a class="xref" href="build_unix_test.html#build_unix_test_sql" title="Building SQL Test Suite on Unix">Building SQL Test Suite on Unix</a> for more information), run the entire test suite by executing the following command in the <code class="literal">../build_unix/sql</code> directory: </p> <pre class="programlisting"> sh ../../test/sql/bdb-test.sh </pre> <p> This runs a set of tests and lists the errors each test encountered, if any. A detailed list of the test results is written to <code class="literal">test.log</code>. </p> <p>To run an individual test, such as insert.test, execute the following command in the <code class="literal">../build_unix/sql</code> directory: </p> <pre class="programlisting"> ./testfixture ../../lang/sql/sqlite/test/insert.test </pre> </div> <div class="sect2" lang="en" xml:lang="en"> <div class="titlepage"> <div> <div> <h3 class="title"><a id="idp1289848"></a>Running SQL Test Suite on Windows</h3> </div> </div> </div> <p> After the test suite is built (see <a class="xref" href="build_win_test.html#build_win_test_sql" title="Building the software needed by the SQL tests">Building the software needed by the SQL tests</a> for more information) and before running the entire test suite, go to <code class="literal">../sql/adapter/bdb-test.sh</code> and edit the line: </p> <pre class="programlisting"> echo $t: `alarm $TIMEOUT ./testfixture.exe $tpath 2>&1 | tee -a test.log | grep "errors out of" || echo "failed"` </pre> <p>to</p> <pre class="programlisting"> echo $t: `alarm $TIMEOUT Win32/Debug/testfixture.exe $tpath 2>&1 | tee -a test.log | grep "errors out of" || echo "failed"` </pre> <p>Running the test suite requires an Unix emulator, such as Cygwin. In a Cygwin window go to the <code class="literal">../build_windows</code> directory and execute the command: </p> <pre class="programlisting"> sh ../sql/adapter/bdb-test.sh </pre> <p>This runs a set of tests and lists errors that each test encountered, if any. A detailed list of the test results is written to <code class="literal">test.log</code>. </p> <p>To run an individual test, such as insert.test, execute the following command in the <code class="literal">../build_windows</code> directory: </p> <pre class="programlisting"> Win32/Debug/testfixture.exe ../sql/sqlite/test/insert.test </pre> </div> </div> </div> <div class="navfooter"> <hr /> <table width="100%" summary="Navigation footer"> <tr> <td width="40%" align="left"><a accesskey="p" href="changelog_4_8.html">Prev</a> </td> <td width="20%" align="center"> </td> <td width="40%" align="right"> <a accesskey="n" href="test_faq.html">Next</a></td> </tr> <tr> <td width="40%" align="left" valign="top">Berkeley DB 4.8.28 Change Log </td> <td width="20%" align="center"> <a accesskey="h" href="index.html">Home</a> </td> <td width="40%" align="right" valign="top"> Test suite FAQ</td> </tr> </table> </div> </body> </html>
Upload File
Create Folder
