How to use getPrefix method of org.testng.reporters.jq.ReporterPanel class

Problem was solved by downgrading the TestNG dependency in build.gradle file from 7.0.1 to 6.14.3

The common solution is to use an @BeforeMethod method to setup test state,

@BeforeMethod
public void setup() {
   i = 0; 
}

Make sure you add @RunWith(PowerMockRunner.class) to the top of your class as well.

::edit:: two years later...

Don't ever use PowerMockito, you shouldn't need to.

If you do need to, you have most likely broken the SOLID principles and your design is wrong.

Fix your design instead.

Usually this information is provided in TestNG report.

If you need this time while running test suite, in @AfterMethod use ITestResult object:

@AfterMethod
public void getRunTime(ITestResult tr) {
    long time = tr.getEndMillis() - tr.getStartMillis();
}

Related: TestNG Dependency injection

If you have a google drive or dropbox accounts, you probably have "dropbox" or "doogle drive" applications installed. Those applications sync contents of your local folders with the cloud. Simply save your screenshots in that folder and you're good to go. Google Drive app Dropbox app

If you experience problem with saving the screenshot itself, please provide the error message you get, or at least a screenshot. I'll be glad to help.

You must set all fields of the test classes to null in tearDown().

The reason is that JUnit instantiates one instance of the test class per test. It keeps that instance around for the whole time to save the results of the test (success, failure, stack trace). So if you use fields, they will stay and you'll run out of memory.

Basically the same answer as rzwitserloot gave but in a different order.

java.lang.NullPointerException

The stack trace complains about a NullPointerException. This means that a reference that should have pointed to an object was not pointing to anything (i.e. the reference was null).

So why was it null? For that you have to look at the next part of the stack trace. Each line describes a method. Each time a new method is called inside another a line is added. The format is <package>.<class>.<method>(<file:line>).

    at java.util.Objects.requireNonNull(Objects.java:203)
    at org.openqa.selenium.support.ui.FluentWait.<init>(FluentWait.java:106)
    at org.openqa.selenium.support.ui.WebDriverWait.<init>(WebDriverWait.java:85)
    at org.openqa.selenium.support.ui.WebDriverWait.<init>(WebDriverWait.java:45)
    at Tests.Test(Tests.java:15)

So the first few lines aren't your code. The first line is from java, the other ones are from selenium. Your code starts at Tests.Test(Tests.java:15).

So what happens at this line?

WebDriverWait wait = new WebDriverWait(driver, 6000);

At this line you are creating a new instance of WebDriverWait. You pass two arguments to the constructor. The second one is a number and clearly not null. The first one driver is a reference to a WebDriver. Because the other argument can't be null, this one probebly is.

So why would driver be null?

You've declared the driver a field in the Hooks class. And by default if you don't assign a value when declaring the field it's value is null.

public class Hooks
{
    public WebDriver driver;

So problem located.

But you say, you are giving driver a value in the Setup method!

public class Hooks
{
    public WebDriver driver;
   @BeforeMethod
    public void Setup() throws InterruptedException
    {
        ...
        WebDriver driver = new ChromeDriver();
        ...
    }

Because you've added WebDriver before driver = new ChromeDriver(); it means you've created a local variable with the same name as the class field driver. Because local variables are more important then class fields the driver name in the Setup method now only refers to the local variable.

To assign the driver to the field you can either use this.driver = driver after creating the new ChromeDriver. Or you can remove WebDriver and only write driver = new ChromeDriver(); to assign the new ChromeDriver to the class field.

According to Maven Surefire Plugin - Running a Single Test :

Running a Set of Methods in a Single Test Class

As of Surefire 2.7.3, you can also run only a subset of the tests in a test class.

NOTE : This feature is supported only for Junit 4.x and TestNG. Use syntax e.g. "foo/MyTest.java", "/MyTest.java", "MyTest" for "test" parameter (see includes/excludes).**

You should use the following syntax:

mvn -Dtest=TestCircle#mytest test

So I think your command should be:

mvn -B clean install -T2C -pl sub-tests -Dtest=!com.xx.xx.test.xx.xx#canMakeCall*

It will ignore all tests methods starting with canMakeCall of test com.xx.xx.test.xx.xx.

Instead of using your surefire configuration with a property, you can:

1. Remove the surefire configuration and replace mvn test -DtestSuite=myCustomSuite.xml by mvn test -Dsurefire.suiteXmlFiles=myCustomSuite.xml. See Surefire documentation
2. Continue to use the mvn test -Dgroups=myGroup.

As the surefire configuration will be removed, the error testSuiteXmlFiles0 has null value won't be present with the -Dgroup option.

You can also use maven profiles which will configure surefire plugin depending on which property you pass to maven.

<profiles>
  <profile>
    <id>suite</id>
    <activation>
      <property>
        <name>testSuite</name>
      </property>
    </activation>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-surefire-plugin</artifactId>
      <configuration>
        <suiteXmlFiles>
          <suiteXmlFile>${testSuite}</suiteXmlFile>
        </suiteXmlFiles>
      </configuration>
    </plugin>
  </profile>
</profiles>