Hi there,
We are using nCrunch version 3.22.0.1 at work and started migrating our codebase to dotnet core/standard recently.
We have one particular library, which relies on NUnit 3.11.0 and includes some internal helper functionality to support our actual test projects. It doesn't contain any tests itself (hence it is dotnet standard). Unfortunately, we link this project in all test projects (some in net472, some in dotenet core 2.2 at this stage).
nCrunch reports build failure for that particular lib and stops processing rest of the test assemblies, which makes nCrunch unusable at this stage.
I am curious if this issue has been addressed already, in a newer version perhaps? If so, that'll be a good reason to upgrade :)
Thanks in advance.
Build/Test Issues
"Analysis failure" for dotnet standard lib with no tests in it
Started by koraybalci on 2,189 views
Remco NCrunch Developer
#13176
06 Mar 2019 06:19 UTC
Hi, thanks for sharing this issue.
To fix this problem, all you should need to do is disable the NUnit adapter in your NCrunch project-level configuration for the netstandard project. In this way NCrunch won't try to discover tests from the project.
This is in the assumption that the error you're receiving is NCrunch complaining about a 'netstandard test project'.
To fix this problem, all you should need to do is disable the NUnit adapter in your NCrunch project-level configuration for the netstandard project. In this way NCrunch won't try to discover tests from the project.
This is in the assumption that the error you're receiving is NCrunch complaining about a 'netstandard test project'.
Perfect, it just worked. Thanks a lot!
Post a reply
Log in to reply.