How to use Interface IPostProcessor class of org.testng.xml package

You need to use dataproviderthreadcount. The threadpoolsize and invocationcount values are not required. See details here.

After some more research I've found the following advantages of TestNG compared to JUnit:

• support for multi threading tests
• better test parameterization
• more detailed reports
• better grouping of tests
• test prioritization
• dependencies between tests (useful for integration test and gui tests)
• much better documentation
• additional setup/teardown levels (@Before/AfterSuite, @Before/AfterTest, @Before/AfterGroup)
• tends to be faster in execution

References:

http://kaczanowscy.pl/tomek/sites/default/files/testng_vs_junit.txt.slidy_.html#(1) http://kaczanowscy.pl/tomek/sites/default/files/2013_junit_and_testng.html#(1) http://softwaretestingguide4u.blogspot.de/2013/01/junit-4-vs-testng.html http://architects.dzone.com/articles/how-i-learned-stop-worrying-0 http://roadtoautomation.blogspot.de/2013/02/testng-vs-junit-4.html

Check dependsOnMethods in the TestNG documentation:

http://testng.org/doc/documentation-main.html#dependencies-with-annotations

If you add this parameter to the second and third test, they won't get executed if the first test failed:

@Test(priority = 1)
public void login() {

}

@Test(priority = 2, dependsOnMethods = {"login"})
public void checkLoginResult() {

}

@Test(priority = 3, dependsOnMethods = {"login"})
public void submitImage() {

}

IAnnotationTransformer or IAnnotationTransformer2 are a better listener choice for your purpose:

public class MyTransformer implements IAnnotationTransformer {

  private final int counter;

  public MyTransformer() {
    String count = System.getProperty("count", "100");
    counter = Integer.parseInt(count);
  }

  public void transform(ITest annotation, Class<?> testClass,
      Constructor testConstructor, Method testMethod) {
    if (testMethod.getName().contains("TC_02_InstructorCreatesCourse")) {
      System.out.println("The listener is activated for:-" + testMethod.getName());
      annotation.setInvocationCount(20);
      System.out.println("Invocation count is set to :-" + counter);
    }
  }
}

Okay, I tried to convert my example to TestNG and it worked for me after following the example at https://code.google.com/p/powermock/wiki/TestNG_usage.

I get the MissingMethodInvocationException you mentioned when I'm omitting the required test class annotation @PrepareForTest(AbstractAnimal.class).

I'm using eclipse 4.4.1 with the TestNG plugin version 6.8.6.

See below for my converted example and the dependencies. Also, notice the extension of PowerMockTestCase. I did not change the sample class AbstractAnimal.

import org.powermock.api.mockito.PowerMockito;
import org.powermock.core.classloader.annotations.PrepareForTest;
import org.powermock.modules.testng.PowerMockTestCase;
import org.testng.Assert;
import org.testng.annotations.Test;

@PrepareForTest(AbstractAnimal.class)
public class AbstractAnimalTest extends PowerMockTestCase {

    @Test
    public void shouldGetMockedHello() {
        PowerMockito.mockStatic(AbstractAnimal.class);
        PowerMockito.when(AbstractAnimal.getHello()).thenReturn("Hello mocked animal world!");

        String greetings = AbstractAnimal.getHello();
        Assert.assertTrue(greetings.equals("Hello mocked animal world!"));
    }

}

Dependendencies (I tried to use your versions):

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>org.gnollix.stackoverflow</groupId>
    <artifactId>mock-static-abstract</artifactId>
    <version>0.0.1-SNAPSHOT</version>

    <dependencies>
        <dependency>
            <groupId>org.testng</groupId>
            <artifactId>testng</artifactId>
            <version>6.8.8</version>
        </dependency>
        <dependency>
            <groupId>org.powermock</groupId>
            <artifactId>powermock-module-testng</artifactId>
            <version>1.5.6</version>
        </dependency>
        <dependency>
            <groupId>org.powermock</groupId>
            <artifactId>powermock-api-mockito</artifactId>
            <version>1.5.6</version>
        </dependency>
    </dependencies>

</project>

Resolved dependencies:

Hope that's useful!

The only problem I see is this, You are reading from excel so may be all the values are coming in String, unless you are converting that to Integer. However, in your test you expect third argument age to be Integer

Changing type to String should resolve the issue

@Test(dataProvider = "newdata")
public void testData(String username, String password, String age) {
        System.out.println(username + " - " + password + " - " + age);
}

The following code would raise the same error.

@DataProvider(name = "newdata")
public static Object[][] getData() {
    return new Object[][]{
            {"20"},
            {"30"}
    };
}

@Test(dataProvider = "newdata")
public void testData(Integer age) {

    System.out.println(age);

}

My strong suggestion would be to run your tests concurrently with the usual JUnit / TestNG tools.

The reason is simple: If a test fails due a race condition, then the test has done it's job perfectly - it has identified a bug in your design, code or concurrency assumptions that you should fix.

Anything that is non-thread-safe that is used simultaneously by multiple test threads (e.g. a mutable static singleton object that is being used on a global basis) is probably a design flaw - you should either make it thread safe or initialise it separately each time as a local object.

Assert.assertSame uses the == operator, which checks that two objects are the same object (have the same reference).

I think you want to use Assert.assertEquals which uses the equals() method, checking if the value of two objects are equal or not.

JUnit has some very helpful examples on their github:

https://github.com/junit-team/junit/wiki/Assertions

Okay, I was able to figure it out. And of course it was incredibly dumb and makes you question all of your years being a software engineer.

The problem was this line:

String className = type.toString();

The value type was of class java.lang.reflect.Type.

Can you see the issue? Don't feel bad if you can't because I couldn't either.

If you run this code:

System.out.println(type.toString());
System.out.println(type.getTypeName());

You end up with the following output:

class java.lang.String
java.lang.String

The issue is quite obvious seeing that, I should be using getTypeName() not toString(). Of course it will throw ClassNotFoundException because class<SPACE> precedes the actual class name.

Yet when I looked at the stacktrace, I overlooked it had class<SPACE> before the name of the class.

Sigh. Good times were had learning about class loaders though.