How to use getPassedTestResults method of org.testng.reporters.EmailableReporter2.TestResult class

The transaction needs to be started in the same thread, here are more details:

Spring3/Hibernate3/TestNG: some tests give LazyInitializationException, some don't

Placing timeouts and wait's are inherently subjective since the time a page takes to load can vary. The best thing you can do is place it in a while loop, but include a large timeout to force the code out of the while loop, or throw an error if the element cannot be found since it is a test after all.

 int i = 0;                        
  while (!driver.findElement(By.xpath(xpathLocator))
    {
    //timeout goes here
    i++;
    if (i == 10) throw new exception
}

something like this should do the trick

You are passing paramter <parameter name="Visit" value="123456"/> in your .xml file and you directly running your TestNG class. So it's not getting that parameter while compiling .

So you need to run your xml suite to provide a valid parameter to your TestNG class.

No. There is no way to make the Spring MVC Test Framework work with external servers (or any actual server for that matter).

As stated in the Spring Reference Manual,

The Spring MVC Test framework provides first class support for testing Spring MVC code using a fluent API that can be used with JUnit, TestNG, or any other testing framework. It’s built on the Servlet API mock objects from the spring-test module and hence does not use a running Servlet container.

The last sentence spells it out: Spring MVC Test does not use a running Servlet container. In fact, it cannot be used with a running Servlet container or any kind of actual server (local or remote).

As an alternative, if you must test against an external server, you could then consider using REST Assured instead of Spring MVC Test for those special cases.

If serializing to a String is an option for you, you can configure GSON to do so with:

GsonBuilder gsonBuilder = new GsonBuilder();
gsonBuilder.setLongSerializationPolicy( LongSerializationPolicy.STRING );
Gson gson = gsonBuilder.create();

This will produce something like:

{numbers : [ "268627104", "485677888", "506884800" ] }

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

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

Try to specify dependsOnGroups for test methods as well.

public class TestClass {

    @Test(groups="B")
    public void b1() {
        System.out.println("b1");
    }

    @Test(groups="B")
    public void b2() {
        System.out.println("b2");
    }

    @Test(groups="A", dependsOnGroups="B")
    public void a1() {
        System.out.println("a1");
    }

    @Test(groups="A", dependsOnGroups="B")
    public void a2() {
        System.out.println("a2");
    }

    @BeforeGroups(value="A", dependsOnGroups="B")
    public void setupA() {
        System.out.println("before");
    }
}

I may be wrong about it, but seems that if a test method that belongs to a group has been picked for execution and it does not depend on any groups or methods, it just causes @BeforeGroups-annotated method to be run (ignoring dependsOnGroups specified there). Note that TestNG does not guarantee the execution order without some explicit declaration, e.g. using "depends" or "priority" mechanisms.

Hopefully, Cedric Beust will pay this question a visit.

@AfterMethod doesn't support priority parameter. But it has dependsOnMethods and dependsOnGroups that can be used instead.

dependsOnMethods

The list of methods this method depends on. There is no guarantee on the order on which the methods depended upon will be run, but you are guaranteed that all these methods will be run before the test method that contains this annotation is run. Furthermore, if any of these methods was not a SUCCESS, this test method will not be run and will be flagged as a SKIP. If some of these methods have been overloaded, all the overloaded versions will be run.

dependsOnGroups

The list of groups this method depends on. Every method member of one of these groups is guaranteed to have been invoked before this method. Furthermore, if any of these methods was not a SUCCESS, this test method will not be run and will be flagged as a SKIP.

In your case dependsOnMethods can be used.

@AfterMethod
public void after2(){
    System.out.println("after2");
}
@AfterMethod(dependsOnMethods = "after2")
public void after1(){
    System.out.println("after1");
}

I don't think it is possible to configure maven-surefire-plugin to rerun passing tests.

However, you can configure the invocation count of a single test using the TestNG (not JUnit) @Test annotation:

@Test(invocationCount = 5)
public void testSomething() {
}

This will result in the testSomething method being tested 5 times.

If you don't want to go the TestNG route, you can refer to this answer for a solution with JUnit.