This makes the invocation of that method happen even if the test is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#... E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod. Cheers,

On 8 May 2013, at 20:46, Adrian Nistor wrote: > @BeforeMethod + alwaysRun=true is indeed pretty wrong and pointless in relation to groups but @AfterMethod + alwaysRun=true seems to make sense given this bit of javadoc: "If set to true, this configuration method will be run even if one or more methods invoked previously failed or was skipped". Does this imply our precious teardown method will be skipped because the test failed unless we add alwaysRun=true? right, that's what I understand as well. Given that it might make sense to add alwaysRun to @AfterMethod as long as you expect it to be invoked in certain situations without the corresponding @BeforeMethod. The situation I'm talking about is when @BeforeMethod doesn't have "alwaysRun" and the owner class is in another test group, e.g.: @Test(groups="functional") class NeverFailIntemittentlyTest { CacgeManager cm; @BeforeMethod void setUp() { cm = new EmbeddedCacheManager(); } @AfterMethod (alwaysRun=true) void tearDown() { cm.stop(); } } If we run all the tests in the "xsite" profile, tearDown will throw NPE as setUp is not invoked. Writing tearDown like this should solve the problem: @AfterMethod (alwaysRun=true) void tearDown() { if (cm != null) cm.stop(); } Cheers, -- Mircea Markus Infinispan lead (www.infinispan.org) _______________________________________________ infinispan-dev mailing list infinispan-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev

On 9 May 2013, at 08:02, Dan Berindei wrote: > Why would TestNG run an @AfterMethod method if the test didn't run? if you set alwaysRun=true on that method it will run it disregarding if the test was run or not. > What method would it run after? not sure i get the question.

Writing tearDown like this should solve the problem: @AfterMethod (alwaysRun=true) void tearDown() { if (cm != null) cm.stop(); }