How to use getName method of org.testng.SuiteRunner class

1.Go to File->Settings-> Plugins>Verify that TestNG-J is enabled. 2.Configure the testNG xml file and provide it as an external source by going to edit configurations and selecting suite and providing the path of the testNG xml you created.

Yes, that's possible. You can create an annotation to specify the parameters this DataProvider should load from your XML.

@Target(ElementType.METHOD)
@Retention(RetentionPolicy.RUNTIME)
public @interface XmlParameters {
   String[] value();    
}

@Test(dataProvider = "XMLFileLoader")
@XmlParameters({"username", "password"})
public void testSomething(String username, String password) {
    // implementation omitted for brevity
}

@DataProvider(name = "XMLFileLoader")
public static Object[][] getDataFromXmlFile(final Method testMethod) {
    XmlParameters parameters = testMethod.getAnnotation(XmlParameters.class);
    String[] fields = parameters.value();
    //load just the fields you want
    return new Object[][] { { "user1", "pass1" } };
}

This code is not "production ready", you should check if the annotation is not null before reading the values, and is probably better move the interface and the logic to load your xml to another class, so you can reuse on another tests.

TestNG has a dependency on JUnit. Therefore junit-4.10.jar is in your class path. This Jar includes Hamcrest classes that are older than Hamcrest 1.3 and are missing some methods. The classloader loads org.hamcrest.core.IsInstanceOf from JUnit and therefore you're running into problems.

Add a dependency to JUnit 4.11 to your POM. This overrides TestNG's dependency to JUnit 4.10 and solves your Hamcrest problems, because JUnit 4.11 no longer includes Hamcrest classes.

<dependency>
  <groupId>junit</groupId>
  <artifactId>junit</artifactId>
  <version>4.11</version>
</dependency>

Disabling "Instrumenting agent" worked for me. To do that you need to disable the async stack traces agent in "Settings | Build, Execution, Deployment | Debugger | Async Stack Traces"

Instead of

import org.apache.log4j.Logger;

use

import org.apache.logging.log4j.Logger;

and define the instance of LOGGER

private static final Logger LOGGER = LogManager.getLogger("HelloWorld");

See this sample http://logging.apache.org/log4j/2.x/manual/api.html

this has nothing todo with Gradle

Try @AfterTest(alwaysRun = true).

From the TestNG doc:

For after methods (afterSuite, afterClass, ...): If set to true, this configuration method will be run even if one or more methods invoked previously failed or was skipped.

I've used both, but I have to agree with Justin Standard that you shouldn't really consider rewriting your existing tests to any new format. Regardless of the decision, it is pretty trivial to run both. TestNG strives to be much more configurable than JUnit, but in the end they both work equally well.

TestNG has a neat feature where you can mark tests as a particular group, and then easily run all tests of a specific group, or exclude tests of a particular group. Thus you can mark tests that run slowly as in the "slow" group and then ignore them when you want quick results. A suggestion from their documentation is to mark some subset as "checkin" tests which should be run whenever you check new files in. I never saw such a feature in JUnit, but then again, if you don't have it, you don't REALLY miss it.

For all its claims of high configuration, I did run into a corner case the a couple weeks ago where I couldn't do what I wanted to do... I wish I could remember what it is, but I wanted to bring it up so you know that it's not perfect.

The biggest advantage TestNG has is annotations... which JUnit added in version 4 anyways.

This was a bug in Testng. solved in 6.9.5. Please upgrade.

Look at the first example of a suite in the TestNG documentation:

<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >

<suite name="Suite1" verbose="1" >
  <test name="Nopackage" >
    <classes>
       <class name="NoPackageTest" />
    </classes>
  </test>

  <test name="Regression1">
    <classes>
      <class name="test.sample.ParameterSample"/>
      <class name="test.sample.ParameterTest"/>
    </classes>
  </test>
</suite>

What is causing your error is verbose="1.0". TestNG tries to parse 1.0 to an int, causing the exception.

You probably want verbose="1" there instead.

As a side note, the TestNG documentation is rather sparse about the verbose attribute. This blogpost does a good job at explaining what values the attribute can have:

Before understanding the usage of verbose attribute, first you have to know the values it can accept. Verbose attribute can takes values from 1 to 10 as shown below:

verbose="1"
verbose="2"
verbose="3"
verbose="4"
verbose="5"
verbose="6"
verbose="7"
verbose="8"
verbose="9"
verbose="10"

If we specify the verbose attribute with smaller number, then the test results log details in the Eclipse IDE -> 'console' window will be less. But if you want to get more details and want to see more clarity on the test results log details in the Eclipse IDE -> 'console' window then you have to assign larger number to the verbose attribute.

Of course, this does not only apply to Eclipse, it is a TestNG configuration.