Reproduction instructions:
Either in the Test Runner window or from the circular icon next to the "TestMethod" attribute, select the "Run" context menu option for the following example unit test.
using Microsoft.VisualStudio.TestTools.UnitTesting;
namespace UnitTestProject1
{
[TestClass]
public class UnitTest1
{
[TestMethod]
public void TestMethod1()
{
Assert.Inconclusive("force an 'Ignored' test result state");
}
}
}
The "Debug" context menu option will now be disabled.
Expected behaviour:
The "Debug" context menu option should be enabled. Ignore should only apply to the "Run test" and "Run test with coverage" options.
Since the code is still compatible and debuggable, why prevent the developer from having the option to decide to debug the test simply on the basis that the prior execution was inconclusive.
Given that the yellow icon already informs the developer that this was the case coderush should let the developer make an informed decision to invoke the debugger, rather than attempting to second guess on the developers behalf that they should not be debugging an inconclusive test.
Regards,
Simon Geering
Hi Simon,
Thank you for pointing out this issue and providing your code sample.
CodeRush Test Runner cannot determine why a test is ignored: the Ignore attribute or the Inconclusive assertion. So, we have decided to remove disabling for all context menu items ("Run test", "Run test with coverage" and "Debug test"). We are working on this change and will inform you on our progress.