Update links

Author: Mikejo5000

docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md

@@ -207,7 +207,7 @@ The code coverage data collector creates a log of which parts of the application
 
 The video data collector captures a screen recording when tests are run. This recording is useful for troubleshooting UI tests. The video data collector is available in **Visual Studio 2017 version 15.5** and later. For an example of configuring this data collector, see the [Example *.runsettings file](#example-runsettings-file).
 
-To customize any other type of diagnostic data adapters, use a [test settings file](../test/collect-diagnostic-information-using-test-settings.md).
+To customize any other type of diagnostic data adapters, use a [test settings file](/previous-versions/visualstudio/visual-studio-2017/test/collect-diagnostic-information-using-test-settings).
 
 ### Blame data collector
 

docs/test/improve-code-quality.md

@@ -95,13 +95,13 @@ Coded UI tests provide a way to create fully automated tests to validate the fun
 Whether you choose best-of-breed Coded UI Tests or generic browser-based UI testing with [Playwright](https://playwright.dev/), Visual Studio provides all the tools you need.
 
 * [Use UI automation to test your code](use-ui-automation-to-test-your-code.md)
-* [Get started creating, editing, and maintaining a coded UI test](walkthrough-creating-editing-and-maintaining-a-coded-ui-test.md)
-* [Test UWP apps with coded UI tests](test-uwp-app-with-coded-ui-test.md)
+* [Get started creating, editing, and maintaining a coded UI test](/previous-versions/visualstudio/visual-studio-2017/test/walkthrough-creating-editing-and-maintaining-a-coded-ui-test)
+* [Test UWP apps with coded UI tests](/previous-versions/visualstudio/visual-studio-2017/test/test-uwp-app-with-coded-ui-test)
 * [Introduction to coded UI tests with Visual Studio Enterprise (Lab)](https://azuredevopslabs.com/labs/tfs/codedui)
 ::: moniker-end
 
 ## Related content
 
 - [Exploratory & manual testing (Azure Test Plans)](/azure/devops/test/index?view=vsts&preserve-view=true)
 - [Load testing (Azure Load Testing)](/azure/load-testing/)
-- [Code analysis tools](../code-quality/code-analysis-for-managed-code-overview.md)
+- [Code analysis tools](/previous-versions/visualstudio/visual-studio-2019/code-quality/code-analysis-for-managed-code-overview)

docs/test/test-execution-with-hot-reload.md

@@ -28,7 +28,7 @@ This is a new way of test execution where we change a widely used path of valida
 ## How it works
 Once the option is enabled, Test Explorer will automatically use test execution with hot reload when possible. If a hot reload is not possible, it will fall back to the regular behavior of building and running tests. As a user running tests, you do not need to make any changes to your workflow (that is, continue to edit code and run tests).
 
-Under the hood, we are using the same [Edit and Continue](../debugger/edit-and-continue.md) infrastructure that exists in the newly released [Hot Reload experience for editing C#/VB code at runtime](https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload/) to determine the changes made. For this reason, we hot reload only when there are no "rude edits", in which case we fall back to building your tests before executing them. For more details on supported edits, read the [Edit and Continue documentation](https://github.com/dotnet/roslyn/blob/296e0fada42f241d338b169c3c6c6189101ef0b7/docs/wiki/EnC-Supported-Edits.md)
+Under the hood, we are using the same [Edit and Continue](/visualstudio/debugger/how-to-enable-and-disable-edit-and-continue) infrastructure that exists in the newly released [Hot Reload experience for editing C#/VB code at runtime](https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload/) to determine the changes made. For this reason, we hot reload only when there are no "rude edits", in which case we fall back to building your tests before executing them. For more details on supported edits, read the [Edit and Continue documentation](https://github.com/dotnet/roslyn/blob/296e0fada42f241d338b169c3c6c6189101ef0b7/docs/wiki/EnC-Supported-Edits.md)
 
 ## How much faster will the test execution be?
 There are many variables that come into play when estimating how much time this feature will save you. For example:

docs/test/using-code-coverage-to-determine-how-much-code-is-being-tested.md

@@ -72,7 +72,7 @@ The code coverage feature is available only in Visual Studio Enterprise edition.
   > - If you're working with unmanaged (native) code, use a debug build.
   > - Generate *.pdb* (symbol) files for each assembly.
 
-If you don't get the results you expect, see [Troubleshoot code coverage](../test/troubleshooting-code-coverage.md).
+If you don't get the results you expect, see [Troubleshoot code coverage](/troubleshoot/developer/visualstudio/ide/troubleshooting-code-coverage).
 
 Don't forget to run code coverage again after updating your code. Coverage results and code coloring aren't automatically updated after you modify your code or when you run tests.
 
@@ -330,10 +330,10 @@ To run tests from the command line, use *vstest.console.exe* utility. Code cover
 
 ## Troubleshoot
 
-If you don't see code coverage results, the [Troubleshoot code coverage](../test/troubleshooting-code-coverage.md) article might help you.
+If you don't see code coverage results, the [Troubleshoot code coverage](/troubleshoot/developer/visualstudio/ide/troubleshooting-code-coverage) article might help you.
 
 ## Related content
 
 - [Customize code coverage analysis](../test/customizing-code-coverage-analysis.md)
-- [Troubleshoot code coverage](../test/troubleshooting-code-coverage.md)
+- [Troubleshoot code coverage](/troubleshoot/developer/visualstudio/ide/troubleshooting-code-coverage)
 - [Unit test your code](../test/unit-test-your-code.md)