Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | 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: |
08864943e72c7eb3dc9fda2798d9342a |
| User & Date: | mistachkin 2011-10-03 00:06:54 |
Context
|
2011-10-03
| ||
| 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 | |
|
2011-10-02
| ||
| 23:56 | Update batch tools to allow precompiled static binaries to be built and packaged. Also, update test procedures web page. Finally, do not use ToLowerInvariant when compiling for the Compact Framework. check-in: 0b847e5208 user: mistachkin tags: trunk | |
Changes
Changes to www/test.wiki.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
..
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
<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) 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>
................................................................................
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>
<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
|
|
>
>
>
>
>
>
>
|
|
|
|
|
|
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
..
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
<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 "<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.
</li>
</ol>
................................................................................
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
|