1
2
3
4
5
6
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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
Building and running tests on Windows
=====================================
**Building Tests**
To build the tests simply navigate to the tests directory above the repo and run,
C:\git\coreclr>build-test.cmd
*Cleaning Tests*
**Note:** Cleaning should be done before all tests to be sure that the test assets are initialized correctly. To do a clean build of the tests, in a clean command prompt, issue the following command:
C:\git\coreclr>build-test.cmd -rebuild
*Building tests that will be precompiled*
C:\git\coreclr>build-test.cmd crossgen
This will use crossgen.exe to precompile the test executables before they are executed.
*Building Other Priority Tests*
C:\git\coreclr>build-test.cmd -priority=2
The number '2' is just an example. The default value (if no priority is specified) is 0. To clarify, if '2' is specified, all tests with CLRTestPriorty 0, 1 AND 2 will be built and consequently run.
**Example**
To run a clean, priority 1, crossgen test pass:
C:\git\coreclr>build-test.cmd -rebuild crossgen -priority=1
**buildtest /?** will list additional supported parameters.
Additionally, there is a Visual Studio solution, `<repo_root>\tests\src\AllTestProjects.sln`, where users can build a particular testcase, or all priority 0 testcases that are within it.
**Building Individual Tests**
Note: buildtest.cmd or build.cmd skipnative skipmscorlib needs to be run atleast once
* Native Test: Build the generated Visual Studio solution or make file corresponding to Test cmake file.
* Managed Test: You can invoke msbuild on the project directly from Visual Studio Command Prompt.
**Running Tests**
In a clean command prompt: `<repo_root>\tests\runtest.cmd`
**runtest /?** will list supported parameters.
This will generate the report named as `TestRun_<arch>_<flavor>.html` (e.g. `TestRun_x64__release.html`) in the current folder. It will also copy all the test dependencies to the folder passed at the command line.
**Investigating Test Failures**
Upon completing a test run, you may find one or more tests have failed.
The output of the Test will be available in Test reports directory, but the default the directory would be something like is `<repo_root>\binaries\tests\x64\debug\Reports\Exceptions\Finalization`.
There are 2 files of interest:
- `Finalizer.output.txt` - Contains all the information logged by the test.
- `Finalizer.error.txt` - Contains the information reported by CoreRun.exe (which executed the test) when the test process crashes.
**Rerunning a failed test**
If you wish to re-run a failed test, please follow the following steps:
1. Set an environment variable, `CORE_ROOT`, pointing to the path to product binaries that was passed to runtest.cmd. The command to set this environment variable is also specified in the test report for a failed test.
2. Next, run the failed test, the command to which is also present in the test report for a failed test. It will be something like `<repo_root>\binaries\tests\x64\debug\Exceptions\Finalization\Finalizer.cmd`.
If you wish to run the test under a debugger (e.g. [WinDbg](http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063(v=vs.85).aspx)), append `-debug <debuggerFullPath>` to the test command. For example:
<repo_root>\binaries\tests\x64\debug\Exceptions\Finalization\Finalizer.cmd -debug <debuggerFullPath>
**Modifying a test**
If test changes are needed, make the change and build the test project. This will binplace the binaries in test binaries folder (e.g. `<repo_root>\binaries\tests\x64\debug\Exceptions\Finalization`). At this point, follow the steps to re-run a failed test to re-run the modified test.
**Authoring Tests (in VS)**
1. Use an existing test such as `<repo_root>\tests\src\Exceptions\Finalization\Finalizer.csproj` as a template and copy it to a new folder under `<repo_root>\tests\src`.
2. Be sure that the AssemblyName has been removed (this causes confusion with the way tests are generally handled behind the scenes by the build system).
3. [Assign a CLRTestKind/CLRTestPriority.](test-configuration.md)
4. Add the project of the new test to `<repo_root>\tests\src\AllTestProjects.sln` in VS
5. Add source files to this newly added project.
6. Indicate the success of the test by returning `100`.
8. Add any other projects as a dependency, if needed.
9. Build the test.
10. Follow the steps to re-run a failed test to validate the new test.
Note:
1. You can disable building of a test per architecture or configuration by using DisableProjectBuild tag in the project. for example:
``<PropertyGroup>``
``<DisableProjectBuild Condition=" '$(Platform)' == 'arm64' ">true</DisableProjectBuild>``
``</PropertyGroup>``
2. To Add Nuget\MyGet Refernces use this (project.json)[https://github.com/dotnet/coreclr/blob/master/tests/src/Common/test_dependencies/project.json]
3. To Build against the mscorlib facade add ``<ReferenceLocalMscorlib>true</ReferenceLocalMscorlib>`` to your project
|
