NCrunch: 1.37.0.46b
Trying that on open sourced project from Code52, https://github.com/Code52/Ideastrike
NCrunch initializes fine, but the IdeaStrike.Tests failed with message
NCrunch: If you are experiencing problems in getting this project to build, have a look at https://www.ncrunch.net/documentation/troubleshooting_project-build-issues
(120): The "Xunit.Runner.MSBuild.xunit" task could not be loaded from the assembly C:\Users\alexander.beletsky\AppData\Local\NCrunch\8056\2\tests\IdeaStrike.Tests\..\..\tools\xunit\xunit.runner.msbuild.dll. Could not load file or assembly 'file:///C:\Users\alexander.beletsky\AppData\Local\NCrunch\8056\2\tools\xunit\xunit.runner.msbuild.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
Remco NCrunch Developer
#1124
09 Feb 2012 09:16 UTC
Hi Alex,
It looks like this project has a custom build step that executes Xunit tests? Likely you would want to disable this for NCrunch builds by making whichever build target triggers it conditional. You can use the $(NCrunch) environment variable - for example:
<Target Name="XUnitTarget" Condition="$(NCrunch) != '1'">
...
</Target>
Otherwise, if you want the target to run, you can probably get it to work by making sure you add "..\..\tools\**.*" to your list of additional files to include for the IdeaStrike.Tests project.
It looks like this project has a custom build step that executes Xunit tests? Likely you would want to disable this for NCrunch builds by making whichever build target triggers it conditional. You can use the $(NCrunch) environment variable - for example:
<Target Name="XUnitTarget" Condition="$(NCrunch) != '1'">
...
</Target>
Otherwise, if you want the target to run, you can probably get it to work by making sure you add "..\..\tools\**.*" to your list of additional files to include for the IdeaStrike.Tests project.
You are absolutely right!
As soon as I temporary removed that target, NCrunch procceded with tests! But, not I have yet another issue.. Probably not related to NCrunch itself, but maybe you know something?
The output:
NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?
External image
As soon as I temporary removed that target, NCrunch procceded with tests! But, not I have yet another issue.. Probably not related to NCrunch itself, but maybe you know something?
The output:
NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?
External image
Remco NCrunch Developer
#1127
09 Feb 2012 10:18 UTC
There are a few things that can cause this. The easiest way to diagnose this issue is to set your log verbosity to detailed then have a look at one of the testing tasks inside the processing queue. The log will usually contain the issue... it could be an internal problem with NCrunch.
Set verbosity to Detailed, but nothing has changed;
Remco NCrunch Developer
#1130
09 Feb 2012 11:00 UTC
Did the log under any of the test tasks show anything interesting that could indicate a failure?
Otherwise, kick through a bug report and I'll take a look at it.
Otherwise, kick through a bug report and I'll take a look at it.
@Remco - I've added in that check for the NCrunch flag and that gets the tests running - I'll send that upstream as a fix in the interim.
@alexanderb - with that flag added, all the tests passing on my local machine. Same version of NCrunch as you.
@alexanderb - with that flag added, all the tests passing on my local machine. Same version of NCrunch as you.
Post a reply
Log in to reply.