Merge pull request #10477 from MicrosoftDocs/main638668838933000510sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/profiling/choose-performance-tool.md

@@ -80,7 +80,7 @@ The following tools are supported with Linux as the target platform as well as W
 The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
 
 - [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md)
-- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
+- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
 - [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
 - [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
 

docs/profiling/optimize-code-using-profiling-tools.md

@@ -198,7 +198,7 @@ Multiple optimizations may be necessary and we can continue to iterate with code
 
 The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
 
-- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
+- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
 - [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
 - [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
 

docs/profiling/what-is-a-profiler.md

@@ -29,7 +29,7 @@ A profiler can help you make informed decisions quickly by providing a visual de
 The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
 
 - [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md)
-- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
+- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
 - [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
 - [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
 

docs/test/debug-unit-tests-with-test-explorer.md

@@ -1,12 +1,13 @@
 ---
 title: Debug unit tests with Test Explorer
 description: Debug and analyze unit tests with Test Explorer in Visual Studio by setting breakpoints to diagnose test method performance issues.
-ms.date: 02/13/2024
+ms.date: 11/08/2024
 ms.topic: how-to
 author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: test-tools
+ms.collection: ce-skilling-ai-copilot
 ---
 # Debug and analyze unit tests with Test Explorer
 
@@ -43,6 +44,20 @@ To diagnose why a test method is taking too much time, select the method in Test
 > This feature is not currently supported for .NET Core.
 ::: moniker-end
 
+::: moniker range=">=vs-2022"
+## 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, select a failed test in Test Explorer, and then do one of the following:
+
+- Choose **Explain failure with Copilot**, or
+- Choose **Debug with Copilot**.
+
+![Screenshot of debugging tests with Copilot.](../test/media/vs-2022/debug-tests-with-copilot.png)
+
+If you debug with Copilot, GitHub Copilot provides you with a debug plan, it sets appropriate breakpoints and watch variables, and it starts the debug session. When the debugger hits the breakpoint, it provides GitHub Copilot with values for the watched variables and Copilot determines your next step: either to continue debugging or fix the problem code. You can continue the Copilot Chat conversation until you have a passing test.
+
+::: moniker-end
+
 ## Related content
 
 - [Unit test your code](../test/unit-test-your-code.md)