**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.
+For example to run all ofthe tests using you checkled build:
+
+`<repo_root>\tests\runtest.cmd checked`
+
+This will generate the report named as `TestRun_<arch>_<flavor>.html` (e.g. `TestRun_Windows_NT__x64__Checked.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`.
+The output of the Test will be available in Test reports directory, but the default the directory would be something like is `<repo_root>\bin\tests\x64\Windows_NT.x64.Checked\Reports\Exceptions\Finalization`.
There are 2 files of interest: