ShuriZma
/
dolphin
mirror of https://github.com/dolphin-emu/dolphin.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Linted markdown

Roger 2016-12-19 02:41:44 -05:00
parent 6abd2e9350
commit 98315f9a72
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Running-Unit-Tests.md

@ -1,4 +1,5 @@
The Dolphin source code contains unit tests that aim to:
* Help find bugs when porting Dolphin to a new platform
* Make refactoring and code changes safer by enforcing API contracts
@ -7,7 +8,6 @@ The tests are located in the `Source/UnitTests` directory and use the [Google Te
For tests that can compare Dolphin to actual hardware, see the [hwtests repository](https://github.com/dolphin-emu/hwtests).
## Running tests on Windows
---
The UnitTests project is compiled as part of the normal build on Windows.
There are a few ways to run the tests:
@ -15,19 +15,20 @@ There are a few ways to run the tests:
1. Using the [GoogleTest Runner](http://visualstudiogallery.msdn.microsoft.com/9dd47c21-97a6-4369-b326-c562678066f0) extension for Visual Studio in order to integrate tests into the Test Explorer. This requires a version of Visual Studio that supports the use of extensions.
2. Invoking execution via msbuild with the `RunUnitTests` property, for example:
```
pushd Source
msbuild /v:m /m /p:Platform=x64 /p:Configuration=Release /p:RunUnitTests=true dolphin-emu.sln
```
3. You can, of course, also go to the UnitTests build output directory and directly run the binary:
```
pushd Build\x64\Release\UnitTests\bin
UnitTests
```
## Running tests on CMake-based systems (Linux / macOS)
---
Use the `unittests` build target: