From 718cac46cda3bacb5636ee319c70e8cfeee78cad Mon Sep 17 00:00:00 2001 From: shuffle2 Date: Thu, 1 Jun 2017 23:33:35 -0700 Subject: [PATCH] vs2017 community edition supports extensions, and point to the latest gtest extension --- Running-Unit-Tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Running-Unit-Tests.md b/Running-Unit-Tests.md index 8cc85ad..08e9297 100644 --- a/Running-Unit-Tests.md +++ b/Running-Unit-Tests.md @@ -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](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. +1. Use the [Test Adapter for Google Test](https://marketplace.visualstudio.com/items?itemName=VisualCPPTeam.TestAdapterforGoogleTest) extension for Visual Studio in order to integrate tests into the Test Explorer. 2. Invoking execution via msbuild with the `RunUnitTests` property, for example: