Hi Remco,
I experimented this morning with the Custom Engine Mode to check if I could exclude some tests based on their category. I think I found a bug with how NCrunch manage test categories in VB.NET. Let met describe the problem.
Let's say I have a test class with two test methods. If I add the category attribute (using the provided workaround) to one of the method, both methods are shown to be within the "Category1" in the NCrunch Tests window
Public Class UnitTest1
<TestMethod()>
Public Sub TestMethod1()
' TODO: Add test logic here
End Sub
<TestProperty("Category", "Category1")>
<TestMethod()>
Public Sub TestMethod2()
End Sub
End Class
The official documentation from MSDN says the TestProperty attribute is supposed to "
Establishes a test specific property on a method." It should not cause the property to be propagated to all the methods of the class. When using the <TestCategory> attribute the VS Tests window correctly shows that only TestMethod2 is categorized.
I'm I doing something wrong?
DB
