You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this is a bug, and pretty nasty one too, because it may or may not manifest depending on the order of tests.
TestNG version 6.8.5.
I have three test classes: BaseTestCase (abstract, implementing BeforeSuite method with alwaysRun=true), FirstSample (which derives from BaseTestCase), and SecondSample (it derives from BaseTestCase too).
This classes are included in suite.xml.
If FirstSample class is annotated with Test(enabled=false), BeforeSuite will probably NOT run.
If SecondSample class is annotated with Test(enabled=false), BeforeSuite will probably run.
Sometimes the order changes, but the rule is the same: two (or more) test classes, deriving from one base class, one of which is annotated with enabled=false.
Hi,
I think this is a bug, and pretty nasty one too, because it may or may not manifest depending on the order of tests.
TestNG version 6.8.5.
I have three test classes: BaseTestCase (abstract, implementing BeforeSuite method with alwaysRun=true), FirstSample (which derives from BaseTestCase), and SecondSample (it derives from BaseTestCase too).
This classes are included in suite.xml.
If FirstSample class is annotated with Test(enabled=false), BeforeSuite will probably NOT run.
If SecondSample class is annotated with Test(enabled=false), BeforeSuite will probably run.
Sometimes the order changes, but the rule is the same: two (or more) test classes, deriving from one base class, one of which is annotated with enabled=false.
Here's the code to reproduce:
BaseTestCase.java:
FirstSample.java:
SecondSample.java:
sample-tests.xml:
The text was updated successfully, but these errors were encountered: