Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix doc display issues. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
6e61cb4b3f3a5bce52f8c84c936500f1 |
| User & Date: | mistachkin 2011-07-11 21:09:16 |
Context
|
2011-07-11
| ||
| 21:19 | Add missing #ifdefs for compact framework (where SQLiteLog is not used). check-in: ee8edc8eb3 user: mistachkin tags: trunk | |
| 21:09 | Fix doc display issues. check-in: 6e61cb4b3f user: mistachkin tags: trunk | |
| 21:03 | Add initial unit testing docs. check-in: a651466562 user: mistachkin tags: trunk | |
Changes
Changes to www/index.wiki.
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
<p> Historical versions, as well as the original support forums, may still be found at <a href="http://sqlite.phxsoftware.com/">http://sqlite.phxsoftware.com/</a>, though there have been no updates to this version since April of 2010. </p> <p> </p> <p> </p> <p> </p> |
> > > > |
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 |
<p> Historical versions, as well as the original support forums, may still be found at <a href="http://sqlite.phxsoftware.com/">http://sqlite.phxsoftware.com/</a>, though there have been no updates to this version since April of 2010. </p> <p> </p> <p> </p> <p> </p> <p> </p> |
Changes to www/test.wiki.
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
..
59
60
61
62
63
64
65
66
67
68
69
70
71
72
|
</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.
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>\Release\bin" for the separate managed
and interop assemblies or
"<root>\bin\<year>\<platform>\Release" for the
mixed-mode assembly).
................................................................................
</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>
|
>
>
>
|
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
..
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
</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. "<root>\bin\<year>\Release\bin" for the separate managed and interop assemblies or "<root>\bin\<year>\<platform>\Release" for the mixed-mode assembly). ................................................................................ </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> |