From 63bedf6ef379559f78cde8568cd53014cbb1a7cb Mon Sep 17 00:00:00 2001 From: PEmu1 Date: Wed, 4 Jan 2017 21:44:00 -0800 Subject: [PATCH] Update links. --- Running-Unit-Tests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Running-Unit-Tests.md b/Running-Unit-Tests.md index 4ac384d..678819d 100644 --- a/Running-Unit-Tests.md +++ b/Running-Unit-Tests.md @@ -3,7 +3,7 @@ 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 -The tests are located in the `Source/UnitTests` directory and use the [Google Test](https://code.google.com/p/googletest/) framework. +The tests are located in the `Source/UnitTests` directory and use the [Google Test](https://github.com/google/googletest) framework. For tests that can compare Dolphin to actual hardware, see the [hwtests repository](https://github.com/dolphin-emu/hwtests). @@ -12,7 +12,7 @@ For tests that can compare Dolphin to actual hardware, see the [hwtests reposito The UnitTests project is compiled as part of the normal build on Windows. 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. +1. Using the [GoogleTest Runner](https://marketplace.visualstudio.com/items?itemName=markusl0.GoogleTestRunner) 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: