<title>Test Procedures</title>
<a name="assumptions"></a>
<h2>Test Assumptions & Prerequisites</h2>
<ol>
<li>
The string "<root>" represents the root of the source tree
(i.e. the working check-out directory) for the System.Data.SQLite project.
</li>
<li>
The string "<year>" represents the version of Visual Studio
used (e.g. "2008" or "2010") to build the binaries being
tested.
</li>
<li>
The string "<configuration>" represents the build
configuration for the binaries being tested (e.g. "Debug" or
"Release").
</li>
<li>
The string "<platform>" represents the native platform for
the binaries being tested (e.g. "Win32" or "x64").
</li>
<li>
The string "<pid>" represents the process identifier for the
instance of EagleShell being used to run the unit tests (e.g.
"1234").
</li>
</ol>
<a name="procedures"></a>
<h2>Test Procedures</h2>
<p>
Follow these steps to unit test the System.Data.SQLite (SDS) binaries.
Unless otherwise noted, all steps need to be done in the order specified.
</p>
<p>
First, you will need a full source check-out for the System.Data.SQLite
project, including the
"<a href="/index.html/dir?name=Externals/Eagle">Externals\Eagle</a>"
directory.
</p>
<p>
The binaries to test must be [./build.wiki | built] or
[./downloads.wiki | downloaded]. If the binaries are downloaded, they must be
placed in the appropriate build output directory (e.g.
"<root>\bin\<year>\<configuration>\bin" for the
separate managed and interop assemblies or
"<root>\bin\<year>\<platform>\<configuration>"
for the mixed-mode assembly).
</p>
<p>
The new unit tests have been setup using <a href="http://eagle.to/">Eagle</a>
and its associated unit testing framework, named "EagleTest". Eagle
is an implementation of the <a href="http://www.tcl.tk/">Tcl</a> scripting
language for the Common Language Runtime (CLR). EagleTest is the unit testing
framework for Eagle, packaged as a collection of Eagle scripts, based loosely
on the implementation of
<a href="http://www.tcl.tk/man/tcl8.4/TclCmd/tcltest.htm">tcltest</a>.
</p>
<a name="automated"></a>
<h2>Automated Unit Tests</h2>
<ol>
<li>Open a normal command prompt window with "cmd.exe".</li>
<li>Change the current directory to "<root>".</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a separate managed and interop assembly:
<b>Externals\Eagle\bin\EagleShell.exe -file Tests\all.eagle</b>
</li>
<li>
Enter the following command to run all the unit tests against the binaries
built with a mixed-mode assembly:
<b>Externals\Eagle\bin\EagleShell.exe -initialize -runtimeOption native -file Tests\all.eagle</b>
</li>
<li>
To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because
the default is to test binaries built with MSBuild 4.0 or Visual Studio
2010) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_year 2008"</b>
</li>
<li>
To test binaries built in the "Debug" build configuration (i.e.
because the default is to test binaries built in the "Release"
build configuration) add the following command line argument right after
"Externals\Eagle\bin\EagleShell.exe" in either of the above
command lines:
<b>-preInitialize "set test_configuration Debug"</b>
</li>
<li>
Make sure all tests pass; the log file
"%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any
errors should occur. EagleTest should produce "success" messages
very similar to the following:<br /><br />
PASSED: 48<br />
TOTAL: 48<br />
PASS PERCENTAGE: 100%<br />
OVERALL RESULT: SUCCESS<br />
</li>
</ol>
