Skip to content

Commit 2e0eadb

Browse files
authored
Merge pull request #1709 from MicrosoftDocs/FromPublicMaster
Confirm merge from FromPublicMaster to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
2 parents e731264 + f062eef commit 2e0eadb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/python/unit-testing-python-in-visual-studio.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This article provides a brief outline of unit testing capabilities in Visual Stu
3333

3434
## Discovering and viewing tests
3535

36-
By convention, Visual Studio identifies tests are as methods whose names start with `test`. To see this behavior, do the following:
36+
By convention, Visual Studio identifies tests as methods whose names start with `test`. To see this behavior, do the following:
3737

3838
1. Open a [Python project](managing-python-projects-in-visual-studio.md) loaded in Visual Studio, right-click your project, select **Add > New Item...**, then select **Python Unit Test** followed by **Add**.
3939

@@ -99,4 +99,4 @@ You can also use the **Analyze Code Coverage for Selected Tests** and **Profile
9999
- When starting debugging, Visual Studio appears to start and stop debugging, and then start again. This behavior is expected.
100100
- When debugging multiple tests, each one is run independently, which interrupts the debugging session.
101101
- Visual Studio intermittently fails to start a test when debugging. Normally, attempting to debug the test again succeeds.
102-
- When debugging, it is possible to step out of a test into the `unittest` implementation. Normally, the next step runs to the end of the program and stop debugging.
102+
- When debugging, it is possible to step out of a test into the `unittest` implementation. Normally, the next step runs to the end of the program and stop debugging.

0 commit comments

Comments
 (0)