Merge pull request #2776 from kendrahavens/patch-3

Change Questions H3 to H2

Author: v-shils

docs/ide/find-code-changes-and-other-history-with-codelens.md

@@ -200,7 +200,7 @@ You can discover unit tests that exist for your C# or Visual Basic code without
 
 1. Go to application code that has associated [unit test code](../test/unit-test-your-code.md).
 
-2. If you have not already, build your application to load the CodeLens test indicators. Make sure [discovery by built assemblies](../test/test-explorer-faq.md#3-assembly-based-discovery-is-no-longer-working-for-my-project-how-do-i-turn-it-back-on) is turned on.
+2. If you have not already, build your application to load the CodeLens test indicators. Make sure [discovery by built assemblies](../test/test-explorer-faq.md#assembly-based-discovery-is-no-longer-working-for-my-project-how-do-i-turn-it-back-on) is turned on.
 
 3. Review the tests for the code by pressing **Alt**+**3**.
 
@@ -321,7 +321,7 @@ To use the keyboard:
 
 ### Q: My CodeLens test indicators no longer appear in my file when I first open my solution. How can I load them?
 
-**A:** Rebuild your project to get CodeLens test indicators to load in your file. Make sure [discovery by built assemblies](../test/test-explorer-faq.md#3-assembly-based-discovery-is-no-longer-working-for-my-project-how-do-i-turn-it-back-on) is turned on. To improve performance, Visual Studio no longer fetches source information for test indicators when code files are loaded. Test indicators are loaded after a build, or when you navigate to a test by double-clicking on it in **Test Explorer**.
+**A:** Rebuild your project to get CodeLens test indicators to load in your file. Make sure [discovery by built assemblies](../test/test-explorer-faq.md#assembly-based-discovery-is-no-longer-working-for-my-project-how-do-i-turn-it-back-on) is turned on. To improve performance, Visual Studio no longer fetches source information for test indicators when code files are loaded. Test indicators are loaded after a build, or when you navigate to a test by double-clicking on it in **Test Explorer**.
 
 ## See also
 

docs/test/test-explorer-faq.md

@@ -19,69 +19,65 @@ manager: douge
 ---
 # Visual Studio Test Explorer FAQ
 
-## Test discovery
-
-### 1. The 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?
+## The 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?
 
   Build your project and make sure assembly-based discovery is turned on in **Tools** > **Options** > **Test**.
 
   [Real time test discovery](https://go.microsoft.com/fwlink/?linkid=862824) is source-based test discovery. It can’t discover tests that use theories, custom adapters, custom traits, `#ifdef` statements, etc. because they are defined at runtime. A build is required for those tests to be accurately discovered. In the 15.6 Previews, assembly-based discovery (the traditional discoverer) runs only after builds. This setting means Real Time Test Discovery discovers as many tests as it can while you are editing, and assembly-based discovery allows dynamically defined tests to appear after a build. Real Time Test Discovery improves responsiveness, but stills allow you to get complete and accurate results after a build.
 
-### 2. What does the '+' (plus) symbol that appears in the top line of Test Explorer mean?
+## What does the '+' (plus) symbol that appears in the top line of Test Explorer mean?
 
   The '+' (plus) symbol indicates that more tests may be discovered after a build as long as assembly-based discovery is turned on. It appears if dynamically defined tests are detected in your project.
 
   ![Plus symbol summary line](media/testex-plussymbol.png)
 
-### 3. Assembly-based discovery is no longer working for my project. How do I turn it back on?
+## Assembly-based discovery is no longer working for my project. How do I turn it back on?
 
   Go to **Tools** > **Options** > **Test** and check the box for **Additionally discover tests from built assemblies after builds.**
 
   ![Assembly-based option](media/testex-toolsoptions.png)
 
-### 4. 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 having to build my project. What changed?
 
   This feature is called [Real time test discovery](https://go.microsoft.com/fwlink/?linkid=862824). It uses a Roslyn analyzer to discover 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 FAQ #1 .
 
-### 5. 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://go.microsoft.com/fwlink/?linkid=862824) only works for the managed languages (C# and Visual Basic), since it is built using the Roslyn compiler. For now, Real Time Test Discovery only works for the xUnit, NUnit, and MSTest frameworks.
 
-### 6. How can I turn on logs for the Test Explorer?
+## How can I turn on logs for the Test Explorer?
 
   Navigate to **Tools** > **Options** > **Test** and find the Logging section there.
 
-### 7. Why are my tests in UWP projects not discovered until I deploy my app?
+## 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 discover tests accurately for UWP projects you not only need to build your project, but also deploy.
 
-### 8. How does sorting test results work in the hierarchy view?
+## How does sorting test results work in the hierarchy view?
 
   The hierarchy view sorts tests alphabetically as opposed to by outcome. The other group by settings normally sort test results by outcome and then alphabetically. See the different group by options in the following image for comparison. You can provide feedback about the design [in this GitHub issue](https://github.com/Microsoft/vstest/issues/1425).
 
   ![SortingExamples](media/testex-sortingex.png)
 
-### 9. In the hierarchy view, there are passed, failed, skipped, and not run icons next to the Project, Namespace, and Class groupings. What do these icons mean?
+## In the hierarchy view, there are passed, failed, skipped, and not run icons next to the Project, Namespace, and Class groupings. What do these icons mean?
 
   The icons next to the Project, Namespace, and Class groupings reflect the state of the tests within that grouping. See the following table.
 
   ![Test Explorer Hierarchy Icons](media/testex-hierarchyicons.png)
 
-### 10. There is no longer a "File Path" filter in the Test Explorer search box.
+## 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 preview 3. This feature had low usage, and the Test Explorer can retrieve test methods faster by excluding this feature. If this change interrupts your development flow, please let us know by submitting feedback on [Developer Community](https://developercommunity.visualstudio.com/).
 
-### 11. In Visual Studio 2017 version 15.8 my tests are discovered, but don't execute.
+## In Visual Studio 2017 version 15.8 my tests are discovered, but don't execute.
 
 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: 
 
 **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 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-preview-relnotes#testadapterextension).
 
-## Features
-
-### How can I turn on feature flags to try out new testing features?
+## How can I turn on feature flags to try out new testing features?
 
 Feature flags are used to ship experimental or unfinished parts of the product to avid users who would like to give feedback before the features ship officially. They may destabilize your IDE experience. Use them only in safe development environments, such as virtual machines. Feature flags are always use-at-your-own-risk settings. You can turn on experimental features with the [feature flags extension](https://marketplace.visualstudio.com/items?itemName=PaulHarrington.FeatureFlagsExtension), or through the developer command prompt.