TestNG BeforeMethod with groups

Question

I am wondering about @BeforeMethod's usage with groups. In http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html it says:

alwaysRun: If set to true, this configuration method will be run regardless of what groups it belongs to.

So I have the following class:

public class BeforeTest {
private static final Logger LOG = Logger.getLogger(BeforeTest.class);
@BeforeMethod(groups = {"g1"}, alwaysRun = false)
public void setUpG1(){
    sleep();
    LOG.info("BeforeMethod G1");
}

@Test(groups = {"g1"})
public void g1Test(){
    sleep();
    LOG.info("g1Test()");
}

@BeforeMethod(groups = {"g2"}, alwaysRun = false)
public void setUpG2(){
    sleep();
    LOG.info("BeforeMethod G2");
}

@Test(groups = {"g2"})
public void g2Test(){
    sleep();
    LOG.info("g2Test()");
}


private void sleep(){
    try {
        Thread.sleep(500);
    } catch (InterruptedException e) {
        e.printStackTrace();
    }
}
}

Which outputs:

BeforeMethod G1
BeforeMethod G2
g1Test()
BeforeMethod G1
BeforeMethod G2
g2Test()

Aside the fact that I think awaysRun is false by default, can anyone explain to me why both before methods are called before each test, disregarding the groups? Something like @Test(skipBeforeMethod = "setUpG1") would work too.

I am using IntelliJ IDEA CE 10.5.2. I've run it with gradle 1.0-milestone-3, too.

score 8 · Answer 1 · answered Mar 13 '20 at 12:34

That is because the groups flag only indicates if a method belongs to a group. When that group is enabled, it is executed always, i.e. before all tests methods irrespective of the group the test methods belong to. By default all groups are enabled.

If you want to have the method only executed for the tests of certain groups, you would need to specify onlyForGroups.

public class BeforeTest {

    private static final Logger LOG = Logger.getLogger(BeforeTest.class);

    @BeforeMethod(onlyForGroups = { "g1" })
    public void setUpG1() {
        sleep();
        LOG.info("BeforeMethod G1");
    }

    @Test(groups = { "g1" })
    public void g1Test() {
        sleep();
        LOG.info("g1Test()");
    }

    @BeforeMethod(onlyForGroups = { "g2" }, alwaysRun = false)
    public void setUpG2() {
        sleep();
        LOG.info("BeforeMethod G2");
    }

    @Test(groups = { "g2" })
    public void g2Test() {
        sleep();
        LOG.info("g2Test()");
    }

    private void sleep() {
        try {
            Thread.sleep(500);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
    }
}

The output is

BeforeMethod G1
g1Test()
BeforeMethod G2
g2Test()

score 3 · Answer 2 · answered Oct 29 '11 at 16:43

3

How are you invoking TestNG? Are you running any groups?

If you run none, both @BeforeMethods will run. If you run "g1", only setupG1 will run, etc...

answered Oct 29 '11 at 16:43

Cedric Beust

15,480
2
55
55

I run none, thought grouping is a kind of filtering so that the beforeMethod with a certain group only applies to tests with the same group. Guess I was wrong. What I need to do is something like your solution here (http://stackoverflow.com/questions/3115822/passing-output-of-one-test-method-to-another-method-testng), but the problem with that solution is that mResult doesn't get resetted if there are many tests depending on f1. – rweng Oct 29 '11 at 16:56

score 2 · Answer 3 · answered Jun 19 '15 at 18:40

I would recommend not to use alwaysRun=true, but create a special group for config methods (we use "config"), and annotate all before*() and after*() methods with groups = "config".

All test methods can be annotated with whatever group you like, e.g. "foo" and "bar".

Then, in your run, you do:

-Dgroups=config,foo

or

-Dgroups=config,bar

If you then add another group, "newGroup", you don't have to go through all the config methods and add "newGroup" to them, you just run:

-Dgroups=config,newGroup

This makes management of groups way easier!

If you (by mistake?) ran something like:

-Dgroups=config,nonExistingGroup

No tests (and no config methods) would run as you actually don't have any tests annotated for "nonExistingGroup" and config methods only run if there are "matching tests" that require those config methods to run.

TestNG BeforeMethod with groups

3 Answers3

Linked