With the release of V3 back in November, we got support for the new MSTest. From the release notes: NCrunch now also has support for the new version of MSTest, including its assembly-level test categories and row tests.
But row tests aren't working for me. Do they only work in VS 2017? Do they only work with .Net Core?
In VS 2015, NCrunch 3.3.0.6 is only running the first two test methods in the repro-case below. The second two test cases that have [DataRow] attributes aren't getting called and show up with white NCrunch "not-run" dots on the left side. MSTest v2 does run them and the Test Explorer shows a separate result for each [DataRow].
using System;
using ClassLibrary1;
using FluentAssertions;
using Microsoft.VisualStudio.TestTools.UnitTesting;
namespace UnitTestProject1
{
[TestClass]
public class NumericExtensionsTests
{
[TestMethod]
public void IsInRange_ValueIsWithinRange()
{
((int)5).EnsureIsInRange(5, 10).Should().BeTrue();
((int)8).EnsureIsInRange(5, 10).Should().BeTrue();
((int)10).EnsureIsInRange(5, 10).Should().BeTrue();
}
[TestMethod]
public void IsInRange_ValueIsNotWithinRange()
{
Action action = () => ((int)4).EnsureIsInRange(5, 10);
action.ShouldThrow<ArgumentOutOfRangeException>()
.Which.ParamName.Should().Be("value");
action = () => ((int)11).EnsureIsInRange(5, 10);
action.ShouldThrow<ArgumentOutOfRangeException>()
.Which.ParamName.Should().Be("value");
}
[TestMethod]
[DataRow(5, 5, 10)]
[DataRow(8, 5, 10)]
[DataRow(10, 5, 10)]
public void IsInRange_ValueIsWithinRangeViaDataRow(int testValue, int min, int max)
{
testValue.EnsureIsInRange(min, max).Should().BeTrue();
}
[TestMethod]
[DataRow(4, 5, 10)]
[DataRow(11, 5, 10)]
public void IsInRange_ValueIsNotWithinRangeViaDataRow(int testValue, int min, int max)
{
Action action = () => testValue.EnsureIsInRange(min, max);
action.ShouldThrow<ArgumentOutOfRangeException>()
.Which.ParamName.Should().Be("value");
}
}
}
