Handling same test class in two test tags of TestNG configuration is not working correctly

[gszczutkowski]

It is not possible run in parallel tests from the same test class when the class is defined in separate test tags of configuration file. Here is the example of testng configuration file:

<suite name="Parallel tests" parallel="tests" thread-count="2">
    <test name="Home Page Tests">
        <parameter name="test-name" value="Home page"/>
        <groups>
            <run>
                <include name="A"/>
            </run>
        </groups>
        <classes>
            <class name="com.testcraftsmanship.utils.SomeFluentTest"/>
        </classes>
    </test>
    <test name="Sequential Tests">
        <parameter name="test-name" value="Home page"/>
        <groups>
            <run>
                <exclude name="A"/>
            </run>
        </groups>
        <classes>
            <class name="com.testcraftsmanship.utils.SomeFluentTest"/>
        </classes>
    </test>
</suite>

Test for veryfying this scenario can be:

public class SomeFluentTest extends FluentTestNg {

    @Test(groups = "A")
    public void shortTest() {
        goTo("https://google.com");
        newInstance(GooglePage.class)
                .getInputField()
                .click();
        waitMillis(3000);
        newInstance(GooglePage.class)
                .getInputField()
                .click();
    }

    @Test(groups = "B")
    public void longTest() {
        goTo("https://google.com");
        newInstance(GooglePage.class)
                .getInputField()
                .click();
        waitMillis(10000);
        newInstance(GooglePage.class)
                .getInputField()
                .click();
    }

    private void waitMillis(int millis) {
        try {
            Thread.sleep(millis);
        } catch (InterruptedException e) {
            e.printStackTrace();
        }
    }

}

class GooglePage extends FluentPage {
    @FindBy(css = "input[title='Search']")
    private FluentWebElement inputField;

    FluentWebElement getInputField(){
        await().until(inputField).clickable();
        return inputField;
    }
}

Actual outcome:
When the first of those two tests is finished then webdriver for the second one is also closed. Exception is thrown: org.openqa.selenium.NoSuchSessionException: Session ID is null. Using WebDriver after calling quit()?

Workaround for this case is to move the test methods from A group to separate test class but It is not very elegant.