Apply suggestions from code review

ghogen · web-flow · commit 1df8cf428882 · 2022-08-30T15:02:39.000-07:00
diff --git a/docs/sharepoint/how-to-add-and-remove-mapped-folders.md b/docs/sharepoint/how-to-add-and-remove-mapped-folders.md
@@ -42,7 +42,6 @@ ms.workload:
 3. In the **Name** box, enter **TestProject1**
 4. Then choose the **Create** button.
 
-
 5. In the **SharePoint Customization Wizard**, choose the **Finish** button to retain the default settings.
 
 6. In **Solution Explorer**, choose the project node, and then, on the menu bar, choose **Project** > **Add SharePoint "Images" Mapped Folder**.
diff --git a/docs/sharepoint/walkthrough-create-a-site-column-content-type-and-list-for-sharepoint.md b/docs/sharepoint/walkthrough-create-a-site-column-content-type-and-list-for-sharepoint.md
@@ -68,7 +68,6 @@ ms.workload:
 
 6. Choose the **Finish** button. The project is now listed in **Solution Explorer**.
 
-
 #### To add site columns
 
 1. Add a new site column. To do this, in **Solution Explorer**, right-click on the **Clinic** project, and then choose **Add** > **New Item**.
diff --git a/docs/test/code-generation-compilation-and-naming-conventions-in-microsoft-fakes.md b/docs/test/code-generation-compilation-and-naming-conventions-in-microsoft-fakes.md
@@ -24,7 +24,6 @@ This article discusses options and issues in Fakes code generation and compilati
 
 - .NET Core, .NET 5.0 or later, and SDK-style project support previewed in Visual Studio 2019 Update 6, and is enabled by default in Update 8. For more information, see [Microsoft Fakes for .NET Core and SDK-style projects](/visualstudio/releases/2019/release-notes#microsoft-fakes-for-net-core-and-sdk-style-projects).
 
-
 ## Code generation and compilation
 
 ### Configure code generation of stubs
diff --git a/docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md b/docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md
@@ -111,7 +111,6 @@ To specify a run settings file in the IDE, select **Test** > **Select Settings F
 
 The file appears on the Test menu, and you can select or deselect it. While selected, the run settings file applies whenever you select **Analyze Code Coverage**.
 
-
 ## Specify a run settings file from the command line
 
 To run tests from the command line, use *vstest.console.exe*, and specify the settings file by using the **/Settings** parameter.
diff --git a/docs/test/create-a-diagnostic-data-adapter-to-collect-custom-data-or-affect-a-test-machine.md b/docs/test/create-a-diagnostic-data-adapter-to-collect-custom-data-or-affect-a-test-machine.md
@@ -21,7 +21,6 @@ You might want to create your own diagnostic data adapter to collect data when y
 
 You can provide default input to your custom diagnostic data adapter using a configuration settings file. For example, you can provide information about the location of the file you want to collect and attach to your test results, or how much disk space you want to be left on the system. This data can be configured for each test settings that you create. You can create your own user control to use as an editor. Any changes that are made to the adapter configuration in your editor are stored with your test settings.
 
-
 If you are running your tests from Visual Studio, you must set these test settings to be active. For more information about test settings, see [Collect diagnostic information using test settings](../test/collect-diagnostic-information-using-test-settings.md).
 
 [!INCLUDE [web-load-test-deprecated](includes/web-load-test-deprecated.md)]
diff --git a/docs/test/create-unit-tests-menu.md b/docs/test/create-unit-tests-menu.md
@@ -22,7 +22,6 @@ The **Create Unit Tests** command creates unit test method stubs. This feature a
 > [!NOTE]
 > The **Create Unit Tests** menu command is only available for C# code. To use this method with .NET Core or .NET Standard, Visual Studio 2019 or later is required.
 
-
 The **Create Unit Tests** menu command is extensible and can be used to generate tests for MSTest, MSTest V2, NUnit, and xUnit.
 
 ## Get started
diff --git a/docs/test/debug-unit-tests-with-test-explorer.md b/docs/test/debug-unit-tests-with-test-explorer.md
@@ -25,14 +25,12 @@ You can use Test Explorer to start a debugging session for your tests. Stepping
 
    ![Test execution details](../test/media/vs-2019/test-explorer-debug.png)
 
-
    For more information, about the debugger, see [Debug in Visual Studio](../debugger/debugger-feature-tour.md).
 
 ## Diagnose test method performance issues
 
 To diagnose why a test method is taking too much time, select the method in Test Explorer and then choose **Profile** on the right-click menu. See [Instrumentation profiling report](../profiling/understanding-instrumentation-data-values.md?view=vs-2017&preserve-view=true).
 
-
 > [!NOTE]
 > This feature is not currently supported for .NET Core.
 
diff --git a/docs/test/getting-started-with-unit-testing.md b/docs/test/getting-started-with-unit-testing.md
@@ -61,7 +61,6 @@ This section describes how to create a unit test project.
    Type **test** in the search box to find a unit test project template for the test framework you want to use, such as **MSTest** (C#) or the **Native Unit Test** project (C++), and select it.
 
 
-
    Starting in Visual Studio 2017 version 14.8, the .NET languages include built-in templates for NUnit and xUnit. For C++, in this example select the **Native Unit Test** project, which uses Microsoft Native Unit Test Framework. (To use a different C++ test framework, see [Writing unit tests for C/C++](../test/writing-unit-tests-for-c-cpp.md)). For Python, see [Set up unit testing in Python code](../python/unit-testing-python-in-visual-studio.md) to set up your test project.
 
    > [!TIP]
@@ -246,7 +245,6 @@ This section describes how to create a unit test project.
    To open Test Explorer, choose **Test** > **Test Explorer** from the top menu bar (or press **Ctrl** + **E**, **T**).
 
 
-
 1. Run your unit tests by clicking **Run All** (or press **Ctrl** + **R**, **V**).
 
    ::: moniker range=">=vs-2022"
diff --git a/docs/test/how-to-collect-intellitrace-data-to-help-debug-difficult-issues.md b/docs/test/how-to-collect-intellitrace-data-to-help-debug-difficult-issues.md
@@ -41,15 +41,13 @@ The data that is collected in the IntelliTrace file increases debugging producti
 
 The following procedure describes how to configure the IntelliTrace data that you want to collect. These steps apply to the Test Settings dialog box in Visual Studio.
 
-
 > [!NOTE]
 > The user account for the test agent that is used to collect IntelliTrace data must be a member of the administrators group. For more information, see [Install and configure test agents](../test/lab-management/install-configure-test-agents.md).
 
 ## Configure the data to collect with the IntelliTrace diagnostic data adapter
 
 Before you perform the steps in this procedure, you must open your test settings from Visual Studio and select the **Data and Diagnostics** page.
 
-
 ### To configure the data to collect with the IntelliTrace diagnostic data adapter
 
 1. Select the role to use to collect IntelliTrace data.
@@ -109,7 +107,6 @@ Before you perform the steps in this procedure, you must open your test settings
     > [!NOTE]
     > To reset the configuration for this diagnostic data adapter, choose **Reset to default configuration** in Visual Studio.
 
-
 ## See also
 
 - [Collect diagnostic data while testing (Azure Test Plans)](/azure/devops/test/collect-diagnostic-data?view=vsts&preserve-view=true)
diff --git a/docs/test/how-to-configure-network-emulation-using-test-settings-in-visual-studio.md b/docs/test/how-to-configure-network-emulation-using-test-settings-in-visual-studio.md
@@ -25,7 +25,6 @@ You can configure the diagnostic data adapter to test your application under var
 
 The following procedure describes how to configure network emulation from the configuration editor. These steps apply to the configuration editor in Visual Studio.
 
-
 > [!NOTE]
 > The network emulation diagnostic data adapter is only applicable to Visual Studio test settings. It is not used for test settings in Microsoft Test Manager (deprecated in Visual Studio 2017).
 
diff --git a/docs/test/how-to-include-recordings-of-the-screen-and-voice-during-tests.md b/docs/test/how-to-include-recordings-of-the-screen-and-voice-during-tests.md
@@ -60,7 +60,6 @@ The screen and voice recorder can be used with either manual or automated tests.
     > [!TIP]
     > To reset the configuration for this diagnostic data adapter, choose **Reset to default configuration** in Visual Studio.
 
-
 ## See also
 
 - [Collect diagnostic data while testing (Azure Test Plans)](/azure/devops/test/collect-diagnostic-data?view=vsts&preserve-view=true)
diff --git a/docs/test/how-to-set-up-your-test-agent-to-run-tests-that-interact-with-the-desktop.md b/docs/test/how-to-set-up-your-test-agent-to-run-tests-that-interact-with-the-desktop.md
@@ -18,7 +18,6 @@ ms.technology: vs-ide-test
 
 If you want to run automated tests that interact with the desktop, you must set up your agent to run as a process instead of a service. For example, if you want to run a coded UI test remotely using a test controller and test agent, or you want to run a test and capture a video recording when you run it, you must set up your agent to run as a process. When you assign agents to roles in your test settings using Visual Studio, you must change the setup for any agents assigned to roles that have to interact with the desktop.
 
-
 [!INCLUDE [web-load-test-deprecated](includes/web-load-test-deprecated.md)]
 
 
diff --git a/docs/test/improve-code-quality.md b/docs/test/improve-code-quality.md
@@ -29,7 +29,6 @@ The **Test Explorer** window helps developers create, manage, and run unit tests
 
 ![Visual Studio Test Explorer 16.2](media/vs-2019/test-explorer-16-2.PNG)
 
-
 * [Get started with unit testing](unit-test-your-code.md)
 * [Unit test basics](unit-test-basics.md)
 * [Run unit tests with Test Explorer](run-unit-tests-with-test-explorer.md)
diff --git a/docs/test/install-third-party-unit-test-frameworks.md b/docs/test/install-third-party-unit-test-frameworks.md
@@ -22,7 +22,6 @@ A Visual Studio solution can contain unit test projects that use different frame
 For .NET, [MSTest, NUnit, and xUnit](getting-started-with-unit-testing.md) are the test frameworks provided by Visual Studio which are installed by default. For C++, a different set of test frameworks are provided, such as CTest.
 
 
-
 ## Acquire frameworks
 
 Install third-party unit test frameworks by using **NuGet Package Manager**.
diff --git a/docs/test/isolating-code-under-test-with-microsoft-fakes.md b/docs/test/isolating-code-under-test-with-microsoft-fakes.md
@@ -32,10 +32,8 @@ Fakes come in two flavors:
 
 - Visual Studio Enterprise
 - A .NET Framework project
-
 - .NET Core, .NET 5.0 or later, and SDK-style project support previewed in Visual Studio 2019 Update 6, and is enabled by default in Update 8. For more information, see [Microsoft Fakes for .NET Core and SDK-style projects](/visualstudio/releases/2019/release-notes#microsoft-fakes-for-net-core-and-sdk-style-projects).
 
-
 > [!NOTE]
 > Profiling with Visual Studio isn't available for tests that use Microsoft Fakes.
 
@@ -280,7 +278,6 @@ Since Microsoft Fakes requires Visual Studio Enterprise, the generation of Fakes
 
 This reference is required to be added manually, specifically to SDK-style projects (.NET Core, .NET 5.0, and .NET Framework) because we've moved to implicitly adding assembly references to your test project. If you follow this method, you need to ensure the fakes assembly is updated when the parent assembly changes.
 
-
 ### Running Microsoft Fakes tests
 
 As long as Microsoft Fakes assemblies are present in the configured `FakesAssemblies` directory (The default being `$(ProjectDir)FakesAssemblies`), you can run tests using the [vstest task](/azure/devops/pipelines/tasks/test/vstest?view=azure-devops&preserve-view=true).

Original file line number	Diff line number	Diff line change
`@@ -18,7 +18,6 @@ ms.technology: vs-ide-test`
`18`	`18`
`19`	`19`	If you want to run automated tests that interact with the desktop, you must set up your agent to run as a process instead of a service. For example, if you want to run a coded UI test remotely using a test controller and test agent, or you want to run a test and capture a video recording when you run it, you must set up your agent to run as a process. When you assign agents to roles in your test settings using Visual Studio, you must change the setup for any agents assigned to roles that have to interact with the desktop.
`20`	`20`
`21`		`-`
`22`	`21`	`[!INCLUDE [web-load-test-deprecated](includes/web-load-test-deprecated.md)]`
`23`	`22`
`24`	`23`