Visual Studio 2022 - not fire unit tests in debug mode

Question

Visual Studio 2022 - not fire unit tests in debug mode

Dani_S 4,896

Hi,

Please see:

https://app.screencast.com/YwqnKkUGuwlR4

How is can be solved?

Thanks,

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Susmitha T (INFOSYS LIMITED) 1,790 Microsoft External Staff

Thank you for reaching out!

You can try to start debugging your tests:

Set Breakpoints: First, set breakpoints in the test methods that you want to debug. Since test methods can run in any order, make sure to set breakpoints in all the relevant test methods.
Use Test Explorer:
- Open Test Explorer in Visual Studio (you can find it under the Test menu > Windows > Test Explorer).
  - Select the test methods you want to debug.
    - Right-click on the selected tests in the pane and select Debug.

This should start a debugging session where you can step through your code and inspect the flow and values.

I'm unable to view the screenshot you attached. Could you please share it again, It will be help us to resolve the issue.

Let me know if you need any further help with this. I will be happy to assist. If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Dani_S 4,896 Reputation points

2025-12-12T09:43:09.0466667+00:00

Thank you very much.

Why I can't do it directly from my code , and use Use Test Explorer ?
Susmitha T (INFOSYS LIMITED) 1,790 Reputation points Microsoft External Staff

2025-12-12T12:26:12.6566667+00:00
Thanks for reaching out!

Unit tests cannot be started directly from the source code because visual studio does not treat a test method like a normal application entry point (such as (Main)).

Instead, tests must be run under a test runner - a special process that discovers, loads, and executes test methods.

This is why you must use test explorer, test -> Debug All Tests, or the test icons that appear in the left margin.

Why debugging tests directly from code is not supported

A test project is not an executable, so Visual Studio cannot start debugging from the test method itself.

You test must be executable by the VSTest test host, which is only triggered by the test explorer or the Test Runner.

Test frameworks (MSTest, xUnit, NUnit) requires the test runner to create the test environment, load attributes, and run setup/teardown.

Because of this, Test Explorer is the correct and only supported way to launch a debugging session.

What you can do directly from the code: You can click the Run/Debug Test icons that show next to test method:

A green Run icon

A purple Debug icon

Visual studio added to make debugging easier, but internally it still uses the Test Explorer easier, but internally it still uses the Test Explorer test runner.

References: Debug Unit Tests with Test Explorer - Visual Studio (Windows) | Microsoft Learn

Run Unit Tests with Test Explorer - Visual Studio (Windows) | Microsoft Learn

Get started with unit testing - Visual Studio (Windows) | Microsoft Learn

Let me know if you need any further help with this. I will be happy to assist. If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Dani_S 4,896 Reputation points

2025-12-12T13:47:14.3033333+00:00
I used this , but icon not appear always? how can cause to show when is not showing?

What you can do directly from the code: You can click the Run/Debug Test icons that show next to test method:

A green Run icon

A purple Debug icon

Visual studio added to make debugging easier, but internally it still uses the Test Explorer easier, but internally it still uses the Test Explorer test runner.
Susmitha T (INFOSYS LIMITED) 1,790 Reputation points Microsoft External Staff

2025-12-15T12:37:05.92+00:00

Thank you for reaching out!

Yes, this is expected behavior in Visual Studio.

The Run (green) and Debug (purple) icons next to a test method are convenience features. They appear only after Visual Studio successfully discovers the test. Test discovery happens in the background and depends on the test SDK, test adapter and test explore services. If discovery is delayed, incomplete, or fails, these icons may not appear.

Regardless of whether the icons are visible, Visual Studio always runs and debug the unit tests in Visual Studio.

When the icons are not shown, using Test Explorer -> Debug selected Tests is reliable and supported approach.

Official Microsoft reference: Debug Unit Tests with Test Explorer - Visual Studio (Windows) | Microsoft Learn

Run Unit Tests with Test Explorer - Visual Studio (Windows) | Microsoft Learn

Let me know if you need any further help with this. I will be happy to assist.
If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
Dani_S 4,896 Reputation points

2025-12-15T12:48:01.5366667+00:00

Thank you very much Susmitha.

Answer 2

If you are having trouble firing unit tests in debug mode in Visual Studio 2022, here are a few steps you can take to troubleshoot the issue:

Set Breakpoints: Ensure that you have set breakpoints in your test methods. Since test methods can run in any order, it's important to set breakpoints in all the test methods you want to debug.
Use Test Explorer: Open Test Explorer by navigating to Test > Windows > Test Explorer. From there, you can select the test methods you want to debug, right-click, and choose Debug.
Check Configuration: Make sure that your project is configured correctly for debugging. Sometimes, issues can arise if the project settings are not set to debug mode.
Rebuild the Project: If the tests are not showing up in Test Explorer, try rebuilding the project to refresh the test list.
Check for Errors: Look for any errors in the Output window that may indicate issues with test discovery or execution. For instance, if you see a ReadOnlySpan error, it may be related to a known MSBuild issue that can be resolved by renaming certain files in the Visual Studio installation directory.
Update Visual Studio: Ensure that you are using the latest version of Visual Studio 2022, as updates often include bug fixes and improvements that may resolve your issue.

If these steps do not resolve the issue, consider consulting the Visual Studio documentation or community forums for additional support.

References:

Share via

Visual Studio 2022 - not fire unit tests in debug mode

1 additional answer

Your answer