Question

There are some test classes which needs to be ignored when I run my testng suite. I tried using the @Test(enabled=false) annotation for the class and methods that needs to be ignored. But my problem is that the class that needs to be ignored extends an abstract class and this abstract class test methods are not ignored even when I have @Test(enabled=false) annotation on the base class. In Junit I could use @ignore on the base class and the test methods on the extended class would not be invoked at all. How can I replicate this behaviour in testng.

Also In my testng suite I run the test by packages and not by classes. Hence even if I try to group the class and ignore the group it is not working either.
<test name="Test">
<groups>
<run>
<exclude name="testClass"/>
</run>
</groups>
<packages>

Please help

Answer 1

I received a response from Cedric on this from the google groups(Testng) . I am pasting it below for reference

Hi Paul,

What you are seeing is an unfortunate consequence of the way inheritance of annotations and default attributes interact with each other in TestNG, and a bug has been filed to make it work better (I don’t have the id handy).

Consider:

@Test(enabled = false)
public class C {
  @Test
  public void f()
}

When TestNG resolves these annotations, it finds that the @Test on the method doesn’t specify “enabled”, so it assigns it its default value. The example becomes:

@Test(enabled = false)
public class C {
  @Test(enabled = true)
  public void f()
}

And now, the value defined at the method level overrides the one specified on the class.

The fix would involve using an enum instead of a boolean (ENABLED, DISABLED, INHERITED, which would be the default), but this would break backward compatibility, so I would need to introduce a new annotation for this (e.g. “runStatus” or something like that), and your example would become

@Test(runStatus = DISABLED)
public class C {
  @Test
  public void f()
}

Does this make sense?

—
Cédric