C# 6.0 project in Visual Studio 2015 using NCrunch 2.11.0.12
I've got two projects. One is the product, the other is the unit tests. I have one unit test as follows:
using FluentAssertions;
using Microsoft.VisualStudio.TestTools.UnitTesting;
namespace UnitTests
{
[TestClass]
public class LineContinuationTests
{
[TestMethod]
public void OrderedListRegExTests()
{
var test = "1";
test.Should().Be("1");
}
}
}
I've used NCrunch quite a bit on other projects so I'm familiar with some of the pitfalls. Tried the usual turn-off parallel execution and copy references stuff.
The test gets queued and appears to be running but never completes. Thoughts?
P.S. This is a small open source project so I can provide the git repo if needed.
Remco NCrunch Developer
#6732
11 Jan 2015 23:40 UTC
Hi,
Thanks for sharing this issue. I'm having some trouble reproducing it on my end ... Are you able to share a code sample? Note that you can submit code through the (- BROKEN LINK -)contact form[/url] if you don't have it shared publicly somewhere.
It's also possible that the execution task is failing but not reporting its status correctly in the Tests Window. Do you see anything of interest in the Processing Queue Window?
Cheers,
Remco
Thanks for sharing this issue. I'm having some trouble reproducing it on my end ... Are you able to share a code sample? Note that you can submit code through the (- BROKEN LINK -)contact form[/url] if you don't have it shared publicly somewhere.
It's also possible that the execution task is failing but not reporting its status correctly in the Tests Window. Do you see anything of interest in the Processing Queue Window?
Cheers,
Remco
Here's the repo
https://github.com/mike-ward/Markdown-Edit.git
Use the V1.3 branch.
Thanks for looking into this.
https://github.com/mike-ward/Markdown-Edit.git
Use the V1.3 branch.
Thanks for looking into this.
Remco NCrunch Developer
#6734
12 Jan 2015 04:13 UTC
Thanks for the repo. I've confirmed that this is being caused by a compatibility issue between .NET 4.5.2 and NCrunch.
To work around this problem, I'd suggest just changing the targeted framework to 4.5.3. It may be enough to simply change this for the test project without touching the production project.
A proper fix for this will be out with the full release of NCrunch 2.11.
To work around this problem, I'd suggest just changing the targeted framework to 4.5.3. It may be enough to simply change this for the test project without touching the production project.
A proper fix for this will be out with the full release of NCrunch 2.11.
Changing just the test project to 4.5.3 worked. Thanks.
Post a reply
Log in to reply.