| Reporter |
Arnold Nelisse (ahwnelisse)
|
|---|---|
| Created | Mar 29, 2012 4:46:06 PM |
| Updated | Mar 30, 2012 3:34:42 PM |
| Priority | Normal |
| Type | Bug |
| Fix versions | Mirabile Futurum |
| State | Submitted |
| Assignee | Victor Kropp (victor.kropp) |
| Subsystem | Unit Testing |
| Affected versions | 6.1.1 |
| Fixed in build | No Fixed in build |
I have both default testfixtures and conditional testfixtures that take longer, so code like this:
[TestFixture]
public class default : SomeBase
{
protected override string Filename { get { return @"filename1"; } }
}
#if LONGTEST
[TestFixture]
public class Longer : SomeBase
{
protected override string Filename { get { return @"filename2"; } }
}
#endif
When opening the solution and navigating to the file no context menus are added for the second testfixture even though LONGTEST is defined in the current configuration. When running all unittests from solution the second fixture is also missing.
After removing the #if statement the context menu's are added. Strangely enough adding the #if statement back does NOT remove the contextmenu. The fixture stays active.
This was ok with version < 6.0 and even in a couple of EAP builds.
[TestFixture]
public class default : SomeBase
{
protected override string Filename { get { return @"filename1"; } }
}
#if LONGTEST
[TestFixture]
public class Longer : SomeBase
{
protected override string Filename { get { return @"filename2"; } }
}
#endif
When opening the solution and navigating to the file no context menus are added for the second testfixture even though LONGTEST is defined in the current configuration. When running all unittests from solution the second fixture is also missing.
After removing the #if statement the context menu's are added. Strangely enough adding the #if statement back does NOT remove the contextmenu. The fixture stays active.
This was ok with version < 6.0 and even in a couple of EAP builds.