Skip to content

Commit f15cc13

Browse files
authored
Screenshot Consistency - Visual Studio 2026 (#15295)
* images * images * images * images
1 parent cdd1c89 commit f15cc13

5 files changed

Lines changed: 21 additions & 5 deletions
58.6 KB
Loading
45.7 KB
Loading
153 KB
Loading
27.5 KB
Loading

docs/test/quick-start-test-driven-development-with-test-explorer.md

Lines changed: 21 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Test-driven development
33
description: Learn how to develop a tested method in C# using Microsoft Test Framework, which you can easily adapt for other languages or test frameworks, such as NUnit.
4-
ms.date: 12/11/2025
4+
ms.date: 04/22/2026
55
ms.topic: how-to
66
ms.author: mikejo
77

@@ -24,7 +24,11 @@ This article demonstrates how to develop a tested method in C# using Microsoft T
2424

2525
Name the test project **MathTests**.
2626

27-
::: moniker range=">=vs-2022"
27+
::: moniker range="visualstudio"
28+
:::image type="content" source="../test/media/visualstudio/test-driven-development-ide.png" alt-text="Screenshot that shows the new code and test projects." lightbox="../test/media/visualstudio/test-driven-development-ide.png":::
29+
::: moniker-end
30+
31+
::: moniker range="vs-2022"
2832
![New code and test projects](../test/media/vs-2022/test-driven-development-ide.png)
2933
::: moniker-end
3034

@@ -84,7 +88,11 @@ This article demonstrates how to develop a tested method in C# using Microsoft T
8488

8589
The details of the test appear in the **Test Detail Summary** pane.
8690

87-
::: moniker range=">=vs-2022"
91+
::: moniker range="visualstudio"
92+
:::image type="content" source="media/visualstudio/test-driven-development-test-detail-summary.png" alt-text="Screenshot of the Test Detail Summary in Test Explorer." lightbox="media/visualstudio/test-driven-development-test-detail-summary.png":::
93+
::: moniker-end
94+
95+
::: moniker range="vs-2022"
8896
![Test Detail Summary in Test Explorer](media/vs-2022/test-driven-development-test-detail-summary.png)
8997
::: moniker-end
9098

@@ -108,7 +116,11 @@ At this point, you've created a test and a stub that you can modify so that the
108116

109117
The solution builds, and the test runs and passes.
110118

111-
::: moniker range=">=vs-2022"
119+
::: moniker range="visualstudio"
120+
:::image type="content" source="../test/media/visualstudio/test-driven-development-passed-test.png" alt-text="Screenshot of the Test Explorer showing a passing test." lightbox="../test/media/visualstudio/test-driven-development-passed-test.png":::
121+
::: moniker-end
122+
123+
::: moniker range="vs-2022"
112124
![Test Explorer showing a passing test](../test/media/vs-2022/test-driven-development-passed-test.png)
113125
::: moniker-end
114126

@@ -236,7 +248,11 @@ Refactor the code, but do not change the tests.
236248

237249
2. Choose **Run All**, and verify that all the tests still pass.
238250

239-
::: moniker range=">=vs-2022"
251+
::: moniker range="visualstudio"
252+
:::image type="content" source="../test/media/visualstudio/test-driven-development-three-passed-tests.png" alt-text="Screenshot of Test Explorer showing three passed tests." lightbox="../test/media/visualstudio/test-driven-development-three-passed-tests.png":::
253+
::: moniker-end
254+
255+
::: moniker range="vs-2022"
240256
![Test Explorer showing 3 passed tests](../test/media/vs-2022/test-driven-development-three-passed-tests.png)
241257
::: moniker-end
242258

0 commit comments

Comments
 (0)