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

Use Factory method with dataProvider method , It create a multiple instance.

 @Factory(dataProvider = "getUrls")
        public SEOErrorFactoryResetBeforeClass(String pagUrl) {
            this.pagUrl = pagUrl;
        }

I use a similar setup, except I am using Dropbox for my repository (just two developers). Just follow these steps, with the m2eclipse (update site: http://m2eclipse.sonatype.org/sites/m2e) and the MercurialEclipse (update site: http://cbes.javaforge.com/update) plugin you can do all in eclipse.

Create a maven project:

File -> New -> Other -> Maven project

In Project explorer right click on the new created maven project

Team -> Share Project... -> Mercurial -> (leave the folder as it is) Finish

Then create an .hgignore file in the project root:

In Project explorer right click on the new created maven project

New -> File -> File Name: .hgignore and Finish

.hgignore:

syntax: regexp
target      # maven output
\.classpath # eclipse
\.project   # eclipse
\.settings  # eclipse
test-output # eclipse junit/testng plugin output

Then you can make your first commit, but beware, hg does not store empty folders in it's repository, so to keep the maven folder structure with no source code in it you have to put a (empty) file in each empty folder, for a simple maven project without any sources it would be in the folders:

• myproject/src/main/java
• myproject/src/main/resources
• myproject/src/test/java
• myproject/src/test/resources

For example I put a file with the name .empty in it with the content "this is a placeholder file, remove if other files are in this folder"

If some of this folders are missing your colleagues would see errors in eclipse if they import your project.

First commit:

In Project explorer right click on the new created maven project

Team -> Commit... -> Select all and enter a commit message -> Finish

Now you can clone it to bitbucket (I don't have experience with bitbucket).

Tell your colleagues to install the two eclipse plugins and then they can get the repo via

File -> New -> Other -> Check out Maven Project from SCM -> enter url to your repo -> Finish

And then you are good to go.

It was a rookie mistake!

In addition to statically importing the class methods, the compiler also required importing of the following classes:

import io.restassured.RestAssured;
import io.restassured.parsing.Parser;

After those declarations, I was able to register the default Parser in the filter_Asset test:

RestAssured.registerParser("text/plain", Parser.JSON);

Faced the same problem. Here is how I resolved it. This seems to be a bug with the new version of the Chrome driver. Using the previous version of the driver (20.0.1133.0) solved this issue for me.

Check the driver download page.

Geb is designed for, and can only be used from, Groovy code. This is mainly due to the dynamic nature of its APIs. What you can choose is which test framework to use (JUnit, TestNG, Spock, etc.). As Geb itself is just a library, it can also be used without a test framework, for example to automate an interaction with a website.

If you need to stick to Java, you'll have to use something like Selenium2, which is what Geb uses under the covers.

Well I was finally able to resolve the issue, although it wasn't so very clear. It turned out the problem was a dependency issue with spring-jersey which had a dependency on spring-aop which in turn had one on spring-asm. I excluded spring-aop from spring-jersey and manually added a dependency to the correct spring-aop version and this solved the issue. Totally not where I expected the problem to be at.

First you have to decide which framework to use: JUnit or TestNG. Once you decided check which @Test annotation are you using. I guess that you marked tests using @Test from TestNG and try to run the tests using JUnit.

You can in general do one of the following:
1) By making the main Thread wait for another Thread using

Thread.join();

2) Making the another Thread as Non Daemon or a user thread:link

Thread.setDaemon(false);

The Java Virtual Machine exits when the only threads running are all daemon threads.This method must be called before the thread is started.

Here is an explanation of what is happening:

You are calling driver.close() in RegisterNewUser. This will close the current window. If no open windows remain, the driver quits. So, when your tearDown calls driver.quit() the session has already ended and you get an error.

Solutions you could use:

• don't call driver.close() in your test and let the teardown handle it

or

• in teardown, check for a valid session and only call driver.quit() if one exists