Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix test for ticket [b4a7ddc83f] by making sure the SQLite core library is shutdown prior to running the tests. Also, more updates to test procedures web page. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
26b210729a9f908a0ed69557a6c73cbc |
| User & Date: | mistachkin 2011-10-03 00:51:55 |
Context
|
2011-10-03
| ||
| 02:23 | Modify unit test infrastructure to work on Mono. Also, fix link in test procedures web page. check-in: a030a6c1db user: mistachkin tags: trunk | |
| 00:51 | Fix test for ticket [b4a7ddc83f] by making sure the SQLite core library is shutdown prior to running the tests. Also, more updates to test procedures web page. check-in: 26b210729a user: mistachkin tags: trunk | |
| 00:06 | More updates to test procedures web page. check-in: 08864943e7 user: mistachkin tags: trunk | |
Changes
Changes to Tests/tkt-b4a7ddc83f.eagle.
13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
runTestPrologue
###############################################################################
package require System.Data.SQLite.Test
runSQLiteTestPrologue
###############################################################################
for {set i 1} {$i < 3} {incr i} {
runTest {test tkt-b4a7ddc83f-1.$i {logging shutdown} -setup [subst {
set appDomainId(1) {[object invoke AppDomain.CurrentDomain Id]}
set fileName {tkt-b4a7ddc83f-1.$i.db}
|
> > > > > > > > > |
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
runTestPrologue ############################################################################### package require System.Data.SQLite.Test runSQLiteTestPrologue ############################################################################### # # NOTE: Make sure that SQLite core library is completely shutdown prior to # starting any of the tests in this file. # object invoke -flags +NonPublic System.Data.SQLite.UnsafeNativeMethods \ sqlite3_shutdown ############################################################################### for {set i 1} {$i < 3} {incr i} { runTest {test tkt-b4a7ddc83f-1.$i {logging shutdown} -setup [subst { set appDomainId(1) {[object invoke AppDomain.CurrentDomain Id]} set fileName {tkt-b4a7ddc83f-1.$i.db} |
Changes to www/test.wiki.
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 .. 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 ... 106 107 108 109 110 111 112 113 114 115 116 117 118 |
<a name="assumptions"></a>
<h2>Test Assumptions & Prerequisites</h2>
<ol>
<li>
The string "<root>" represents the root of the source tree
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 "<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.
</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 enlistment for the System.Data.SQLite
project, including the
"<a href="http://system.data.sqlite.org/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.
................................................................................
</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: 30<br />
TOTAL: 30<br />
PASS PERCENTAGE: 100%<br />
OVERALL RESULT: SUCCESS<br />
</li>
</ol>
|
| | > | | | | |
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 .. 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 ... 107 108 109 110 111 112 113 114 115 116 117 118 119 |
<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 "<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="/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.
................................................................................
</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: 46<br />
TOTAL: 46<br />
PASS PERCENTAGE: 100%<br />
OVERALL RESULT: SUCCESS<br />
</li>
</ol>
|