Skip to content

Commit ea77abe

Browse files
committed
Merged main into live
2 parents 4e5e52d + 22675c8 commit ea77abe

File tree

5 files changed

+19
-4
lines changed

5 files changed

+19
-4
lines changed

docs/profiling/choose-performance-tool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ The following tools are supported with Linux as the target platform as well as W
8080
The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
8181

8282
- [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md)
83-
- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
83+
- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
8484
- [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
8585
- [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
8686

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -198,7 +198,7 @@ Multiple optimizations may be necessary and we can continue to iterate with code
198198

199199
The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
200200

201-
- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
201+
- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
202202
- [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
203203
- [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
204204

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ A profiler can help you make informed decisions quickly by providing a visual de
2929
The following articles and blog posts provide more information to help you learn to use the Visual Studio performance tools effectively.
3030

3131
- [Case study: Beginner's guide to optimizing code](../profiling/optimize-code-using-profiling-tools.md)
32-
- [Isolate a performance issue](../profiling/isolate-performance-issue.md)
32+
- [Case study: Isolate a performance issue](../profiling/isolate-performance-issue.md)
3333
- [Improving Visual Studio performance with the new Instrumentation Tool](https://devblogs.microsoft.com/visualstudio/improving-visual-studio-performance-with-the-new-instrumentation-tool/)
3434
- [Case Study: Double performance in under 30 minutes](https://devblogs.microsoft.com/visualstudio/case-study-double-performance-in-under-30-minutes/)
3535

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

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,13 @@
11
---
22
title: Debug unit tests with Test Explorer
33
description: Debug and analyze unit tests with Test Explorer in Visual Studio by setting breakpoints to diagnose test method performance issues.
4-
ms.date: 02/13/2024
4+
ms.date: 11/08/2024
55
ms.topic: how-to
66
author: mikejo5000
77
ms.author: mikejo
88
manager: mijacobs
99
ms.subservice: test-tools
10+
ms.collection: ce-skilling-ai-copilot
1011
---
1112
# Debug and analyze unit tests with Test Explorer
1213

@@ -43,6 +44,20 @@ To diagnose why a test method is taking too much time, select the method in Test
4344
> This feature is not currently supported for .NET Core.
4445
::: moniker-end
4546

47+
::: moniker range=">=vs-2022"
48+
## Get AI assistance to debug tests
49+
50+
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:
51+
52+
- Choose **Explain failure with Copilot**, or
53+
- Choose **Debug with Copilot**.
54+
55+
![Screenshot of debugging tests with Copilot.](../test/media/vs-2022/debug-tests-with-copilot.png)
56+
57+
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.
58+
59+
::: moniker-end
60+
4661
## Related content
4762

4863
- [Unit test your code](../test/unit-test-your-code.md)
Loading

0 commit comments

Comments
 (0)