edit pass: test-explorer-articles

ShawnJackson · ShawnJackson · commit c780b2f288aa · 2024-12-12T12:41:08.000-06:00
diff --git a/docs/test/debug-unit-tests-with-test-explorer.md b/docs/test/debug-unit-tests-with-test-explorer.md
@@ -28,16 +28,16 @@ You can use Test Explorer to start a debugging session for your tests. Stepping
    ![Screenshot that shows test execution details.](../test/media/vs-2019/test-explorer-debug.png)
    ::: moniker-end
 
-For more information, about the debugger, see [Debug in Visual Studio](../debugger/debugger-feature-tour.md).
+For more information about the debugger, see [Debug in Visual Studio](../debugger/debugger-feature-tour.md).
 
 ## Diagnose performance problems with a test method
 
 ::: moniker range=">=vs-2022"
-Starting in Visual Studio 2022 version 17.8, you can use any applicable tool in the Performance Profiler to help improve your code, and not just the Instrumentation tool. You can profile small units of work in isolation, make changes, and then remeasure and validate the impact of the change.
+Starting in Visual Studio 2022 version 17.8, you can use any applicable tool in the Performance Profiler to help improve your code, and not just the Instrumentation tool. You can profile small units of work in isolation, make changes, and then remeasure and validate the impact of the changes.
 
 To diagnose why a test method is taking more time than you'd like, or using more memory than you'd like:
 
-1. Select the method in Test Explorer, right-click on the pane, and then select **Profile**.
+1. Right-click the method in Test Explorer, and then select **Profile**.
 1. In the Performance Profiler, select a profiling tool to test your code.
 
 For more information, see [this blog post](https://devblogs.microsoft.com/visualstudio/a-unit-of-profiling-makes-the-allocations-go-away/) or see [Collect profiling data without debugging](../profiling/running-profiling-tools-with-or-without-the-debugger.md#collect-profiling-data-without-debugging).
@@ -46,7 +46,7 @@ For more information, see [this blog post](https://devblogs.microsoft.com/visual
 ::: moniker range="vs-2019"
 To diagnose why a test method is taking too much time:
 
-- Select the method in Test Explorer, right-click on the pane, and then select **Profile**.
+- Right-click the method in Test Explorer, and then select **Profile**.
 
 For more information, see [Instrumentation profiling report](../profiling/understanding-instrumentation-data-values.md?view=vs-2017&preserve-view=true).
 
@@ -58,17 +58,17 @@ For more information, see [Instrumentation profiling report](../profiling/unders
 
 ## Get AI assistance to debug tests
 
-Starting in Visual Studio 2022 version 17.12 Preview 2, you can get quick assistance from GitHub Copilot to debug tests if you have an [active Copilot subscription](../ide/visual-studio-github-copilot-chat.md#prerequisites). To get help, right-click a failed test in Test Explorer, and then do one of the following:
+Starting in Visual Studio 2022 version 17.12 Preview 2, you can get quick assistance from GitHub Copilot to debug tests if you have an [active Copilot subscription](../ide/visual-studio-github-copilot-chat.md#prerequisites). To get help, right-click a failed test in Test Explorer, and then select of the following commands:
 
-- Select **Explain failure with Copilot**.
-- Select **Debug with Copilot**.
+- **Explain failure with Copilot**
+- **Debug with Copilot**
 
 ![Screenshot of debugging tests with Copilot.](../test/media/vs-2022/debug-tests-with-copilot.png)
 
 If you debug with GitHub Copilot:
 
 1. It provides you with a debug plan.
-1. It sets appropriate breakpoints and watch variables
+1. It sets appropriate breakpoints and watch variables.
 1. It starts the debug session.
 
 When the debugger hits the breakpoint, it provides GitHub Copilot with values for the watched variables. Copilot then determines your next step: either continue debugging or fix the problem code. You can continue the Copilot Chat conversation until you have a passing test.
diff --git a/docs/test/test-explorer-faq.md b/docs/test/test-explorer-faq.md
@@ -1,5 +1,5 @@
 ---
-title: Review Test Explorer FAQ issues and answers
+title: Review Test Explorer FAQ Issues and Answers
 description: Review frequently asked questions (FAQs) about Visual Studio Test Explorer, which include some common troubleshooting scenarios.
 ms.date: 06/25/2020
 ms.topic: conceptual
@@ -19,109 +19,117 @@ ms.subservice: test-tools
 
 ## Dynamic test discovery
 
-**Test Explorer is not discovering my tests that are dynamically defined. (For example, theories, custom adapters, custom traits, #ifdefs, etc.) How can I discover these tests?**
+**Test Explorer is not discovering my tests that are dynamically defined (for example, theories, custom adapters, custom traits, and #ifdef statements). How can I discover these tests?**
 
 Build your project to run assembly-based discovery.
 
-[Real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/) is source-based test discovery. It can’t discover tests that use theories, custom adapters, custom traits, `#ifdef` statements, and more because they're defined at run time. A build is required for those tests to be accurately found. In Visual Studio 2017 version 15.6 and later, assembly-based discovery (the traditional discoverer) runs only after builds. This setting means real-time test discovery finds as many tests as it can while you're editing, and assembly-based discovery allows dynamically defined tests to appear after a build. Real-time test discovery improves responsiveness, but still allows you to get complete and precise results after a build.
+[Real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/) is source-based test discovery. It can't discover tests that use theories, custom adapters, custom traits, `#ifdef` statements, and more because they're defined at runtime. A build is required for those tests to be accurately found.
 
-## Test Explorer '+' (plus) symbol
+In Visual Studio 2017 version 15.6 and later, assembly-based discovery (the traditional discoverer) runs only after builds. This setting means real-time test discovery finds as many tests as it can while you're editing. Assembly-based discovery allows dynamically defined tests to appear after a build.
 
-**What does the '+' (plus) symbol that appears in the top line of Test Explorer mean?**
+Real-time test discovery improves responsiveness, but it still allows you to get complete and precise results after a build.
 
-The '+' (plus) symbol indicates that more tests may be discovered after a build when assembly-based discovery runs. This symbol appears if dynamically defined tests are detected in your project.
+## Test Explorer plus (+) symbol
 
-![Plus symbol summary line](media/testex-plussymbol.png)
+**What does the plus symbol that appears in the top line of Test Explorer mean?**
+
+The plus (+) symbol indicates that more tests might be discovered after a build when assembly-based discovery runs. This symbol appears if dynamically defined tests are detected in your project.
+
+![Screenshot that shows a summary line with a plus symbol.](media/testex-plussymbol.png)
 
 ## Real-time test discovery
 
-**Tests now appear in Test Explorer while I type, without having to build my project. What changed?**
+**Tests now appear in Test Explorer while I type, without requiring me to build my project. What changed?**
 
-This feature is called [Real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/). It uses a Roslyn analyzer to find tests and populate Test Explorer in real time, without requiring you to build your project. For more information about test discovery behavior for dynamically defined tests such as theories or custom traits, see [Dynamic test discovery](#dynamic-test-discovery).
+This feature is called [real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/). It uses a Roslyn analyzer to find tests and populate Test Explorer in real time, without requiring you to build your project. For more information about test discovery behavior for dynamically defined tests such as theories or custom traits, see [Dynamic test discovery](#dynamic-test-discovery) earlier in this article.
 
-## Real-time test discovery compatibility
+## Compatibility for real-time test discovery
 
-**What languages and test frameworks can use Real Time Test Discovery?**
+**What languages and test frameworks can use real-time test discovery?**
 
-[Real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/) only works for the managed languages (C# and Visual Basic), since it's built using the Roslyn compiler. For now, real-time test discovery only works for the xUnit, NUnit, and MSTest frameworks.
+[Real-time test discovery](https://devblogs.microsoft.com/dotnet/real-time-test-discovery/) works only for the managed languages (C# and Visual Basic), because it's built via the Roslyn compiler. For now, real-time test discovery works only for the xUnit, NUnit, and MSTest frameworks.
 
 ## Test Explorer logs
 
-**How can I turn on logs for the Test Explorer?**
+**How can I turn on logs for Test Explorer?**
 
-Navigate to **Tools** > **Options** > **Test** and find the Logging section there.
+Go to **Tools** > **Options** > **Test** and find the **Logging** section there.
 
 ## UWP test discovery
 
 **Why are my tests in UWP projects not discovered until I deploy my app?**
 
-UWP tests target a different runtime when the app is deployed. This means that to find tests accurately for UWP projects you not only need to build your project, but also deploy.
+Universal Windows Platform (UWP) tests target a different runtime when the app is deployed. To find tests accurately for UWP projects, you need to not only build your project but also deploy it.
 
 ## Test Explorer sorting
 
 **How does sorting test results work in the hierarchy view?**
 
-The hierarchy view sorts tests alphabetically as opposed to by outcome. Previous group by settings sorted test results by outcome and then alphabetically. You can still enable sorting by outcome by right-clicking on the column header in Test Explorer, enabling the State column, and then clicking on the State column header to apply sorting on that column. You can provide feedback about the design in this [GitHub issue](https://github.com/Microsoft/vstest/issues/1425).
+The hierarchy view sorts tests alphabetically, not by outcome. Previous group-by settings sorted test results by outcome and then alphabetically. You can still enable sorting by outcome by right-clicking the column header in Test Explorer, enabling the **State** column, and then selecting the **State** column header to apply sorting on that column. You can provide feedback about the design in [this GitHub issue](https://github.com/Microsoft/vstest/issues/1425).
 
 ## Test Explorer hierarchy view
 
-**In the hierarchy view, there are passed, failed, skipped, and not run icons next to parent-node groupings. What do these icons mean?**
+**In the hierarchy view, there are passed, failed, skipped, and not-run icons next to parent-node groupings. What do these icons mean?**
 
-The icons next to the Project, Namespace, and Class groupings show the state of the tests within that grouping. See the following table.
+The icons next to the **Project**, **Namespace**, and **Class** groupings show the state of the tests within that grouping. See the following table.
 
-![Test Explorer Hierarchy Icons](media/testex-hierarchy-icons.png)
+![Table of Test Explorer hierarchy icons.](media/testex-hierarchy-icons.png)
 
 ## Search by file path
 
-**There is no longer a "File Path" filter in the Test Explorer search box.**
+**Why is there is no longer a file path filter in the Test Explorer search box?**
 
-The file path filter in the **Test Explorer** search box was removed in Visual Studio 2017 version 15.7. This feature had low usage, and Test Explorer can retrieve test methods faster by leaving out this feature. If this change interrupts your development flow, let us know by submitting feedback on [Developer Community](https://aka.ms/feedback/suggest?space=8).
+The file path filter in the Test Explorer search box was removed in Visual Studio 2017 version 15.7. This feature had low usage, and Test Explorer can retrieve test methods faster by leaving it out. If this change interrupts your development flow, let us know by submitting feedback on [Developer Community](https://aka.ms/feedback/suggest?space=8).
 
-## Remove undocumented interfaces
+## Removal of undocumented interfaces
 
 **Some test-related APIs are no longer present in Visual Studio 2019. What changed?**
 
-In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented will be removed. They were marked as "deprecated" in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, very few extensions had found these APIs and taken a dependency on them. These include `IGroupByProvider`, `IGroupByProvider<T>`, `KeyComparer`, `ISearchFilter`, `ISearchFilterToken`, `ISearchToken`, and `SearchFilterTokenType`. If this change affects your extension, let us know by filing a bug on [Developer Community](https://aka.ms/feedback/suggest?space=8).
+In Visual Studio 2019, some test window APIs that were previously marked public but were never officially documented were removed. They were marked as deprecated in Visual Studio 2017 to give extension maintainers an early warning. To our knowledge, very few extensions found these APIs and took a dependency on them. They include `IGroupByProvider`, `IGroupByProvider<T>`, `KeyComparer`, `ISearchFilter`, `ISearchFilterToken`, `ISearchToken`, and `SearchFilterTokenType`.
+
+If this change affects your extension, let us know by filing a bug on [Developer Community](https://aka.ms/feedback/suggest?space=8).
 
 ## Test adapter NuGet reference
 
-**In Visual Studio 2017 version 15.8 my tests are discovered, but don't execute.**
+**Why don't my tests run in Visual Studio 2017 version 15.8, even though they're discovered?**
 
-All test projects must include their .NET test adapter NuGet reference in their .csproj file. If they don't, the following test output appears on the project if discovery by a test adapter extension is kicked off after a build, or if the user tries to run the selected tests:
+All test projects must include their .NET test adapter NuGet reference in their .csproj file. If they don't, the following test output appears on the project if discovery by a test adapter extension starts after a build, or if the user tries to run the selected tests:
 
 **Test project {} does not reference any .NET NuGet adapter. Test discovery or execution might not work for this project. It is recommended to reference NuGet test adapters in each .NET test project in the solution.**
 
-Instead of using test adapter extensions, projects are required to use test adapter NuGet packages. This requirement greatly improves performance and causes fewer issues with continuous integration. Read more about .NET Test Adapter Extension deprecation in the [release notes](/visualstudio/releasenotes/vs2017-relnotes-v15.8#testadapterextension).
+Instead of using test adapter extensions, projects are required to use test adapter NuGet packages. This requirement greatly improves performance and causes fewer problems with continuous integration. Read more about the deprecation of .NET test adapter extensions in the [release notes](/visualstudio/releasenotes/vs2017-relnotes-v15.8#testadapterextension).
 
-## UWP TestContainer was not found
+## UWP TestContainer not found
 
-**My UWP tests are no longer being executed in Visual Studio 2017 version 15.7 and later.**
+**Why are my UWP tests no longer running in Visual Studio 2017 version 15.7 and later?**
 
-Recent UWP test projects specify a test platform build property that allows better performance for identifying test apps. If you have a UWP test project that was initialized before Visual Studio version 15.7, you may see this error in **Output** > **Tests**:
+Recent UWP test projects specify a build property that allows better performance for identifying test apps. If you have a UWP test project that was initialized before Visual Studio version 15.7, you might see this error in **Output** > **Tests**:
 
 **System.AggregateException: One or more errors occurred. ---> System.InvalidOperationException: The following TestContainer was not found {} at Microsoft.VisualStudio.TestWindow.Controller.TestContainerProvider \<GetTestContainerAsync>d__61.MoveNext()**
 
 To fix this error:
 
-- Update your test project build property using the following code:
+- Update the build property for your test projects by using the following code:
+
+  ```XML
+  <UnitTestPlatformVersion Condition="'$(UnitTestPlatformVersion)' == ''">$(VisualStudioVersion)</UnitTestPlatformVersion>
+  ```
 
-```XML
-<UnitTestPlatformVersion Condition="'$(UnitTestPlatformVersion)' == ''">$(VisualStudioVersion)</UnitTestPlatformVersion>
-```
+- Update the TestPlatform SDK version by using the following code:
 
-- Update the TestPlatform SDK version using the following code:
+  ```XML
+  <SDKReference Include="TestPlatform.Universal, Version=$(UnitTestPlatformVersion)" />
+  ```
 
-```XML
-<SDKReference Include="TestPlatform.Universal, Version=$(UnitTestPlatformVersion)" />
-```
+## Preview features
 
-## Using preview features
+**How can I use preview features in Visual Studio 2019?**
 
-In Visual Studio 2019, you can opt into preview features in **Tools > Options > Environment > Preview Features**.
+In Visual Studio 2019, you can opt in to preview features in **Tools** > **Options** > **Environment** > **Preview Features**.
 
 ## Related content
 
 - <xref:Microsoft.VisualStudio.TestTools.UnitTesting?displayProperty=fullName>
 - [Create and run unit tests for existing code](/previous-versions/dd293546(v=vs.110))
 - [Unit test your code](unit-test-your-code.md)
-- [Live unit testing FAQ](live-unit-testing-faq.yml)
+- [FAQ for live unit testing](live-unit-testing-faq.yml)
