NCrunch: This test reported an inconclusive result. You can adjust whether NCrunch should treat this result as a pass by using the 'Consider inconclusive tests as passing' NCrunch project-level configuration setting.
Microsoft.VisualStudio.TestTools.UnitTesting.AssertInconclusiveException: Assert.Inconclusive failed.
Set to False and then to True does not fix the problem.
Even resetting all settings and removing all ncrunch related files does not change the behaviour of this single tests.
can you help me?
I can assist you with by running custom builds of ncrunch if needed.
public abstract class TestBase
{
[TestMethod, ExpectedException(typeof(Exception))]
public virtual void SomeTest()
{
// all good
Assert.AreEqual(1, 1);
}
}
[TestClass]
public class Test : TestBase
{
[TestMethod]
public override void SomeTest()
{
Assert.Inconclusive();
}
}
The expectation of the thrown exception in the base class is forcing the test to fail, even the test itself is overwritten.
I'm currently the only one using ncrunch in my team so I just ignore the problem for now.
That also means that I could be your beta tester of V3 if you agree!
jschreuder wrote:
Sorry to go off topic, but is the licence policy on major versions any different? Or if I've bought a key in the last 12 months it will work for v3?
There will be no change to licensing or pricing. You could effectively consider it the same as 2.24.
(Un)fortunately, there were a few other things that needed to be fixed in NCrunch rather urgently, so v2.24 has just been released with a fix for this issue.