Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | More comment updates to test suite. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
5f2352effea20cd0e053798abe0c0851 |
| User & Date: | mistachkin 2011-09-03 15:36:40 |
Context
|
2011-09-07
| ||
| 10:31 | Support LINQ queries with EndsWith method, fix for [59edc1018b]. Add test to verify the behavior from ticket [00f86f9739]. Modify test results/handling for ticket [8b7d179c3c] to be consistent with these new tests. check-in: 7810393e98 user: mistachkin tags: trunk | |
|
2011-09-03
| ||
| 15:36 | More comment updates to test suite. check-in: 5f2352effe user: mistachkin tags: trunk | |
| 14:58 | Add more comments to the unit test infrastructure. Cleanup and modularize use of the test configuration. check-in: a9046f0f02 user: mistachkin tags: trunk | |
Changes
Changes to Tests/common.eagle.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
..
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
#
###############################################################################
if {[isEagle]} then {
proc getBuildYear {} {
#
# NOTE: See if the "year" setting has been overridden by the user (e.g. on
# the command line). This controls which binaries we are testing,
# those produced by either the Visual Studio 2008 or Visual Studio
# 2010 build systems. To override this value via the command line,
# enter a command similar to one of the following (all on one line):
#
# EagleShell.exe -preInitialize "set test_year 2008"
# -file .\path\to\all.eagle
#
# EagleShell.exe -preInitialize "set test_year 2010"
# -file .\path\to\all.eagle
#
................................................................................
return [expr {[haveConstraint imageRuntime40] ? "2010" : "2008"}]
}
}
proc getBuildConfiguration {} {
#
# NOTE: See if the "configuration" setting has been overridden by the user
# (e.g. on the command line). This controls which binaries we are
# testing, those produced with the Debug or Release build types. To
# override this value via the command line, enter a command similar
# to one of the following (all on one line):
#
# EagleShell.exe -preInitialize "set test_configuration Debug"
# -file .\path\to\all.eagle
#
# EagleShell.exe -preInitialize "set test_configuration Release"
# -file .\path\to\all.eagle
#
|
|
>
|
|
|
|
|
>
|
|
|
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
..
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
#
###############################################################################
if {[isEagle]} then {
proc getBuildYear {} {
#
# NOTE: See if the "year" setting has been overridden by the user (e.g. on
# the command line). This helps control exactly which set of
# binaries we are testing, those produced using either the Visual
# Studio 2008 or Visual Studio 2010 build systems. To override this
# value via the command line, enter a command similar to one of the
# following (all on one line):
#
# EagleShell.exe -preInitialize "set test_year 2008"
# -file .\path\to\all.eagle
#
# EagleShell.exe -preInitialize "set test_year 2010"
# -file .\path\to\all.eagle
#
................................................................................
return [expr {[haveConstraint imageRuntime40] ? "2010" : "2008"}]
}
}
proc getBuildConfiguration {} {
#
# NOTE: See if the "configuration" setting has been overridden by the user
# (e.g. on the command line). This helps control exactly which set
# of binaries we are testing (i.e. those built in the "Debug" or
# "Release" build configurations). To override this value via the
# command line, enter a command similar to one of the following (all
# on one line):
#
# EagleShell.exe -preInitialize "set test_configuration Debug"
# -file .\path\to\all.eagle
#
# EagleShell.exe -preInitialize "set test_configuration Release"
# -file .\path\to\all.eagle
#
|