Sdk: Enable debugging of tests with dotnet test

[livarcocc]

Find a way to allow for debugging when using dotnet test

[moozzyk]

A --debug flag that allows you to attach to the process might be the first step

[programatt]

Currently the only way I was able to get debugging in visual studio was to add System.Diagnostics.Debugger.Launch(); to the source. Is that seriously the only way to debug anything right now?

[moozzyk]

@programatt - you can also do Console.WriteLine() :imp:

[cdmihai]

+1

[livarcocc]

We have added a dotnet test debug experience in VS.

[masaeedu]

@livarcocc Is this documented somewhere?

[RemiBou]

@livarcocc is this documented ? or is this issue still opened ?

[livarcocc]

I am not sure about the documentation. But it is just like any other tests in VS.

[masaeedu]

@livarcocc I don't really understand what you mean. If you've added a "dotnet test debug experience", how is a user supposed to invoke it? I'd imagine there's some command line flag or options you have to pass to dotnet test, but I can't see this documented anywhere.

[livarcocc]

What I mean is that you can do that in VS, but not in the command line.

[bobbyg603]

Documentation would be really helpful here! I haven't been able to figure this one out.

[fedoranimus]

@livarcocc Why is this issue closed? As far as I can tell, the issue hasn't actually been resolved as described.

[livarcocc]

What I mean is that you can discover tests for core in VS and debug them through VS.

[fedoranimus]

Ah, okay.

I guess I assumed this issue was more about being able to add a flag such as --debug to dotnet test in order to allow the debugging of all discovered test cases via the CLI for use in applications like VSCode.

[NightOwl888]

What I mean is that you can discover tests for core in VS and debug them through VS.

And what about tests that don't fail in Visual Studio but fail when running dotnet test? How do we debug those?

[omarpiani]

nunit3-console https://github.com/nunit/docs/wiki/Console-Command-Line has --debug option.

I think that's really easy and useful if you want to debug without visual studio or for some other (buggy) reason!

Reopen this!!!

[fedoranimus]

I agree that the issue has not been resolved and should be reopened.

[livarcocc]

Please, file an issue under microsoft/vstest for this.

[smbecker]

I came across this issue because I was looking for a way to debug tests launched from the command line. I came across this line that indicates that if you set $env:VSTEST_RUNNER_DEBUG=1 then you can use dotnet test and it will wait for the debugger to attach before continuing execution. I verified that this does work. Hopefully this is helpful for others.

[YairHalberstadt]

Setting $env:VSTEST_HOST_DEBUG=1 allows you to debug the actual tests being run

[hananiel]

Setting $env:VSTEST_HOST_DEBUG=1 allows you to debug the actual tests being run

on linux/mac: export VSTEST_HOST_DEBUG=1

[jaydpather]

You can add an entry point to your Unit Test project, in a file called Program.fs (for F#). I was able to debug my NUnit tests like this:

namespace BackendTest

open RebelSoftware.UnitTests.ControllerTests

module Program =
[]
let main args =
//this entry point is the only way to debug unit tests
let employeeControllerTest = EmployeeControllerTest()
employeeControllerTest.Setup()
employeeControllerTest.ReturnsResponseFromMQWhenRequestBodyIsValid()
0

[mhlavacek]

I came across this issue because I was looking for a way to debug tests launched from the command line. I came across this line that indicates that if you set $env:VSTEST_RUNNER_DEBUG=1 then you can use dotnet test and it will wait for the debugger to attach before continuing execution. I verified that this does work. Hopefully this is helpful for others.

I almost got this to work. When I try to attach vs 2019 complains about vstest.console.pdb not being loaded. Then all my breakpoints become the "red outline circles" instead of being filled in letting me know the breakpoint will not be hit.

The UX for all this isn't very good and I wish there was better documentation\solutions for attaching a debugger to 'dotnet test' execution.