Fatal error debugging tests via Test-Explorer #320

bunnu · 2017-05-04T08:50:40Z

Thanks for your work getting nunit3-vs-adapter running with .net core. Running tests via dotnet test or Test-Explorer in VS seems to work fine.

When i try to debug a test via Test-Explorer a Message-Box with following Message appears:

A fatal error has occurred and debugging needs to be terminated. For more details, please see the Microsoft Help and Support web site. HRESULT=0x8000ffff. ErrorCode=0x0

I'm using VS 2017 V15.1 (26403.79) and referencing following packages:

<PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />
<PackageReference Include="Moq" Version="4.7.9" />
<PackageReference Include="NUnit" Version="3.6.1" />
<PackageReference Include="NUnit3TestAdapter" Version="3.8.0-alpha1" />

The text was updated successfully, but these errors were encountered:

mikebeaton · 2017-05-05T11:10:50Z

(FWIW I can debug individual tests with 3.8-alpha in my setup, so this problem is not universal. I don't know if it is relevant, but I am not using Moq, and I have VS Professional 2017 15.0.0+26228.9.)

rprouse · 2017-05-05T12:26:46Z

Debugging is one of the main tests before releasing, so it is definately not universal.

Can you post your entire CSPROJ file here to see?
Do you have a minimum reproducible example that I can debug?
Does debug all work?
Can you try downloading https://github.com/rprouse/NUnitPlatformTests and see debugging in that solution works?

We need to identify what is different about your project or setup so that we can fix this 👍

bunnu · 2017-05-05T13:00:58Z

Hi Rob,

I'm little bit confused: The solution, which was generating the mentioned fatal error yesterday, is working today. I'm quite sure I didn't change anything (code, extensions, packages, etc.). My co-worker had the same issue yesterday. Today it is working too?! I'm also able to debug all your tests in the NUnitPlatformTests-Solution.

Currently I'm not able to reproduce the error.

rprouse · 2017-05-05T13:19:10Z

@bunnu don't you love working with .NET Core? Thanks for letting me know. I am going to keep this issue open for a bit so others can confirm if it is an issue or not. Maybe it just required a restart of Visual Studio? I do

@Gerfaut can you let us know if it is working for you yet? If not, can you answer any of my questions that I posted above?

bunnu · 2017-05-05T13:30:46Z

My first try yesterday was restarting Visual Studio, but it didn't solved the problem. Maybe the antivirus caused the issue? I'm using Kaspersky Endpoint Security 10. @Gerfaut which AV are you using?

ghost · 2017-05-05T15:32:22Z

Hi @rprouse,

I have the exact same behavior than @bunnu, my previous try is now working... but I succeed to recreate the problem.
Here are the step to do it:

Inside a folder, dotnet new sln
Open the sln with Visual Studio 2017
From Visual Studio, create a new Class Lib project.
Edit the .csproj to add the dependencies (so I am not using Nuget). The csproj is then the following:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />
    <PackageReference Include="NUnit" Version="3.6.1" />
    <PackageReference Include="NUnit3TestAdapter" Version="3.8.0-alpha1" />
  </ItemGroup>

</Project>

When I build the solution, those lines are added in the csproj:

<ItemGroup> 
    <Service Include="{82a7f48d-3b50-4b1e-b82e-3ada8210c358}" /> 
  </ItemGroup>

I try to launch one dummy test and it crashes with the error above.
When I close and relaunch Visual Studio, I can debug the test without error. The only file that changed is the Test.NETCoreNunit\ClassLibrary1\bin\Debug\netcoreapp1.1\nunit_random_seed.tmp which was "1972429476" and now contains "971211234" (tracked with GIT).

My AV is BitDefender Endpoint Security Tools but I don't think there is a issue with this :)

Does it help a bit ?
Do you need the full project (which should work then) ?

Thanks!

rprouse · 2017-05-05T16:43:09Z

@Gerfaut thanks for the detailed report. My guess is that it is a Visual Studio or .NET Core tooling bug, but I am going to leave this open to confirm. Personally, Visual Studio 2017 is very buggy working with .NET Core. It often crashes or exhibits weird behaviour whenever I edit the CSPROJ files, so it could be related.

For your other comments, the Service tag is added to all test project by Visual Studio. It is intended to speed up test discovery. The nunit_random_seed.tmp file allows for repeatable test runs when using NUnit's random features. It can be ignored.

ghost · 2017-05-06T06:19:27Z

Hi @rprouse,
Thanks for explanation! If I succeed to find more information, I'll complete it here.
Anyway, you should be right about the VS2017 / .NET Core Tooling bug.
Let's see!

Thanks a lot!!

NightOwl888 · 2017-05-07T12:42:37Z

I had the same problem. Here is my project file:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp1.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="15.0.0" />
    <PackageReference Include="NUnit" Version="3.6.1" />
    <PackageReference Include="NUnit3TestAdapter" Version="3.8.0-alpha1" />
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\TestNUnit\TestNUnit.csproj" />
  </ItemGroup>

  <ItemGroup>
    <Service Include="{82a7f48d-3b50-4b1e-b82e-3ada8210c358}" />
  </ItemGroup>

</Project>

It kept producing the same error message as above as many times as I ran it. Then I read some of the posts here that said "overnight it stopped happening". I decided to close Visual Studio 2017 and reopen it and then it started working. So, it looks like this probably isn't a problem with the test adapter, but a caching issue of some sort in Visual Studio.

rprouse · 2017-05-07T19:16:43Z

@NightOwl888 thanks for the update. It is definately looking like a Visual Studio issue, but I am going to leave this issue open for a bit so others can find it easily.

ircnelson · 2017-05-23T13:29:15Z

I had the same problem with xUnit and solved this problem changing project type from Library to Console Application:

<PropertyGroup Label="Configuration" Condition="'$(Configuration)|$(TargetFramework)|$(Platform)'=='Debug|netcoreapp1.1|AnyCPU'">
  <OutputType>exe</OutputType>
</PropertyGroup>

<PropertyGroup>
  <TargetFrameworks>netcoreapp1.1;net461</TargetFrameworks>
  <AssemblyName>MyProject.UnitTests</AssemblyName>
  <ApplicationIcon />
  <OutputTypeEx>exe</OutputTypeEx>
  <StartupObject />
</PropertyGroup>

My final csproj: https://gist.github.com/ircnelson/9cbddb681d520d7f581dbfc99709a9e1

giggio · 2017-06-06T22:04:26Z

I can confirm that changing from Library to Console App solves the problem.

OsirisTerje · 2017-06-25T18:21:47Z

Following @Gerfaut 's recipe (Thanks, that was to the point!!!) , and updating to NUnit 3.7.1, and adapter 3.8.0-alpha1 I can confirm it still fails.

I am pretty sure this is VS, so I'll contact them about it. It might be related to the adapter, that we're not acting the way we should (but don't know yet - A little bit of Kafka here), so I'll keep it open.

PS:
Thanks also to @giggio , @ircnelson , @mikebeaton , @NightOwl888 and @bunnu for the feedback, it really helps when more can confirm and elaborate on the issues!

OsirisTerje · 2017-06-25T20:23:12Z

FWIW: Sometimes I manage to get into some sort of fallback property pages dialog (right clicking the csproj - but only now and then, not sure what is triggering this), and inside that one I can set the Debug Target (to the csproj to debug), and then it all works. I can't yet find that value stored anywhere however, but if anyone have any clues to this:

Delpak · 2017-10-25T19:25:29Z

I had exactly the same problem. But after clean and rebuild the solution, the problem was solved.

zhenyu-siama · 2017-10-29T23:20:08Z

I had extactly the same issue. Not with NUnit, but XUnit. (So it is a Visual Studio issue, not NUnit issue!)

It was all good last Friday (2017-10-27). This morning (2017-10-30), it crashes whenever I start a debug from test explorer. I could not fix it by restarting Visual Studio or restarting windows.

I did the rebuild as suggested by Delpak, it worked. The error is gone. So try clean & rebuild. Good luck!

OsirisTerje · 2017-10-30T08:28:14Z

@navin22 says this is probably related to microsoft/vstest#558

joost-morsink · 2017-12-05T09:57:27Z

For me, removing the <Service Include="{GUID}"... solved the problem, at least temporarily.

k-s-s · 2018-03-09T19:35:25Z

Had this issue with latest VS 15.6.1
Solved with setting test projecct (Class Library) startup object to NUnit.Program, run a test (fails), then revert the setting back to Not Set

jnm2 · 2018-03-20T01:10:21Z

@k-s-s Is your issue the one fixed in 15.6.3?

https://developercommunity.visualstudio.com/content/problem/209020/last-update-studion-2017-cannot-run-nunit-tests.html

TheCodechimp · 2018-04-12T20:15:07Z

I apologize if someone already mentioned this, but I encountered this error while trying to debug some Azure functions. You can run into this error if you specify a .NET framework version but have the function API specified to V2.
<PropertyGroup> <TargetFramework>net461</TargetFramework> <AzureFunctionsVersion>v2</AzureFunctionsVersion> <== This will cause it to throw the error. Fix is to just change it to V1 </PropertyGroup>

shargon · 2018-04-17T16:06:26Z

I have the same issue :(

MY SOLUTION

I had a wrong workingDirectory in launchsettings.json

{
  "profiles": {
    "NeoVM.Interop.Tests": {
      "commandName": "Project",
      "workingDirectory": "C:\\Sources\\Neo\\neo-hypervm\\tests\\NeoVM.Interop.Tests\\bin\\Debug\\netcoreapp2.0",
      "nativeDebugging": true
    }
  }
}

prudhviraj299 · 2018-08-09T15:05:48Z

Cleaning Project resolved my issue.
If this doesn't work restart VS and then clean project before debugging.

OsirisTerje · 2018-08-09T16:36:44Z

Close this for now, as there is nothing we can do. Feel free to add links to work-arounds.

aleha84 · 2018-09-17T11:56:37Z

VS 2017 Pro. Version: 15.8.4 Still reproducing. Using NUnit 3.10.1.
Used solution from here

In my case with Visual Studio 2017 release version the unit test project failed with this error because for some reason the unit test project had a launchsettings.json file under the project "properties" folder. Deleting it resolved the debugging issue.

OsirisTerje · 2018-09-17T13:24:49Z

@aleha84 That project uses an outdated project format. Create a new project and check if it works for you. You can clone and check this one: https://github.com/OsirisTerje/DotNetCoreTestExample

VictorioBerra · 2019-01-24T16:50:49Z

@aleha84 Thank you!

My issues was my test projects had a launchsettings!

This is because before the fixes in 2.2 we were told for our tests, we need to target the .Web SDK. So as I converted everything over back to the normal SDK those files remained.

freerider7777 · 2019-02-21T15:51:17Z

I had this issue with VS 2017, Nunit3
My test project had in Build -> Platform target x64. I switched to Any CPU and everything is ok :)

adamsproul · 2019-02-21T20:05:35Z

Removing the IIS Express profile from the launchsettings.json fixed this issue for me.

bunnu changed the title ~~Fatal error debugging Tests via Test-Explorer~~ Fatal error debugging tests via Test-Explorer May 4, 2017

bunnu mentioned this issue May 5, 2017

Support for .Net Core projects #297

Closed

rprouse added confirm We need a separate confirmation of this issue is:bug labels May 5, 2017

OsirisTerje added VS Issue and removed confirm We need a separate confirmation of this issue labels Jun 25, 2017

jayaranigarg mentioned this issue Jul 18, 2017

Debugging XUnit test cases fails critically microsoft/vstest#558

Closed

cijothomas mentioned this issue May 1, 2018

Fix Visual Studio crash when debugging xunit tests microsoft/ApplicationInsights-aspnetcore#661

Closed

5 tasks

OsirisTerje added External Tracked here, but must be fixed in external tool closed:SomebodyElsesProblem Closed because there is nothing we can do, as this is caused by an external component labels Aug 9, 2018

OsirisTerje closed this as completed Aug 9, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fatal error debugging tests via Test-Explorer #320

Fatal error debugging tests via Test-Explorer #320

bunnu commented May 4, 2017

mikebeaton commented May 5, 2017

rprouse commented May 5, 2017

bunnu commented May 5, 2017 •

edited

Loading

rprouse commented May 5, 2017

bunnu commented May 5, 2017

ghost commented May 5, 2017

rprouse commented May 5, 2017

ghost commented May 6, 2017

NightOwl888 commented May 7, 2017 •

edited

Loading

rprouse commented May 7, 2017

ircnelson commented May 23, 2017 •

edited

Loading

giggio commented Jun 6, 2017

OsirisTerje commented Jun 25, 2017

OsirisTerje commented Jun 25, 2017

Delpak commented Oct 25, 2017 •

edited

Loading

zhenyu-siama commented Oct 29, 2017 •

edited

Loading

OsirisTerje commented Oct 30, 2017

joost-morsink commented Dec 5, 2017

k-s-s commented Mar 9, 2018

jnm2 commented Mar 20, 2018

TheCodechimp commented Apr 12, 2018 •

edited

Loading

shargon commented Apr 17, 2018 •

edited

Loading

prudhviraj299 commented Aug 9, 2018

OsirisTerje commented Aug 9, 2018

aleha84 commented Sep 17, 2018

OsirisTerje commented Sep 17, 2018

VictorioBerra commented Jan 24, 2019

freerider7777 commented Feb 21, 2019

adamsproul commented Feb 21, 2019

Fatal error debugging tests via Test-Explorer #320

Fatal error debugging tests via Test-Explorer #320

Comments

bunnu commented May 4, 2017

mikebeaton commented May 5, 2017

rprouse commented May 5, 2017

bunnu commented May 5, 2017 • edited Loading

rprouse commented May 5, 2017

bunnu commented May 5, 2017

ghost commented May 5, 2017

rprouse commented May 5, 2017

ghost commented May 6, 2017

NightOwl888 commented May 7, 2017 • edited Loading

rprouse commented May 7, 2017

ircnelson commented May 23, 2017 • edited Loading

giggio commented Jun 6, 2017

OsirisTerje commented Jun 25, 2017

OsirisTerje commented Jun 25, 2017

Delpak commented Oct 25, 2017 • edited Loading

zhenyu-siama commented Oct 29, 2017 • edited Loading

OsirisTerje commented Oct 30, 2017

joost-morsink commented Dec 5, 2017

k-s-s commented Mar 9, 2018

jnm2 commented Mar 20, 2018

TheCodechimp commented Apr 12, 2018 • edited Loading

shargon commented Apr 17, 2018 • edited Loading

prudhviraj299 commented Aug 9, 2018

OsirisTerje commented Aug 9, 2018

aleha84 commented Sep 17, 2018

OsirisTerje commented Sep 17, 2018

VictorioBerra commented Jan 24, 2019

freerider7777 commented Feb 21, 2019

adamsproul commented Feb 21, 2019

bunnu commented May 5, 2017 •

edited

Loading

NightOwl888 commented May 7, 2017 •

edited

Loading

ircnelson commented May 23, 2017 •

edited

Loading

Delpak commented Oct 25, 2017 •

edited

Loading

zhenyu-siama commented Oct 29, 2017 •

edited

Loading

TheCodechimp commented Apr 12, 2018 •

edited

Loading

shargon commented Apr 17, 2018 •

edited

Loading