How to use assertLength method of org.testng.FileAssert class

According to official TestNG documentation, see "Command Line Parameters" table here http://testng.org/doc/documentation-main.html#running-testng , it should be possible with:

$ mvn test -Dexcludegroups=group3

However, for greater flexibility I would recommend to use test suite configuration file (aka testng.xml), the location of which can be configured via <suiteXmlFile> property of surefire-plugin, see: http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html

This will allow to take a full control over groups inclusion/exclusion, see: http://testng.org/doc/documentation-main.html#exclusions

There really isn't a "good" way to do this. The best thing I can suggest would be TestNG, which allows you to annotate your test methods and cause them to be executed in n threads concurrently. For example:

@Test(invocationCount=10, threadPool=10)
public void testSomethingConcurrently() {
    ...
}

My TestNG knowledge is rusty at best, but AFAIK that should invoke the testSomethingConcurrently method 10 times concurrently. This is a nice and declarative way to run multi-threaded tests against your code.

You can of course do something similar in JUnit by spawning threads manually in a loop, but that's insanely ugly and difficult to work with. I had to do this once for a project I was working on; those tests were a nightmare to deal with since their failures weren't always repeatable.

Concurrency testing is difficult and prone to frustration, due to its non-deterministic nature. This is part of why there is such a big push these days to use better concurrency abstractions, ones which are easier to "reason about" and convince one's self of correctness.

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.

This was not possible until now. I have fixed this in the latest snapshot version of TestNG. It should be available in the upcoming version of TestNG (Any version greater than 7.0.0)

The issue that I created to track this : https://github.com/cbeust/testng/issues/2199

In a nutshell, you can do the following :

• Implement the interface org.testng.IInjectorFactory
• Plugin the fully qualified class name of the newly created implementation via the command line argument -dependencyinjectorfactory

I encountered a problem with similar symptoms today. I'm not sure if it is the same problem but it matches everything in your question.

In my case, the log files said:

!ENTRY org.eclipse.core.jobs 4 2 2015-12-03 15:49:19.369
!MESSAGE An internal error occurred during: "Launching NewTest".
!STACK 0
java.lang.NullPointerException
at org.testng.eclipse.maven.MavenTestNGLaunchConfigurationProvider.getVMArgsFromPom(MavenTestNGLaunchConfigurationProvider.java:74)

So my problem was that the TestNG-plugin in Eclipse failed to find the pom-file, as I don't use Maven. Anyway, after uninstalling the optional M2E (Maven...) part of the TestNG Eclipse plugin I could run my TestNG test cases successfully.

If you have the same issue, you uninstall the M2E part in Eclipse by selecting

• Help
• Install new software...
• What is already installed?
• Select the TestNG M2E software and click uninstall

Hope this helps!

Your tests are not in the default test sources directory src/test/java. See:

https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html

myModule/src/main/test/java/ClientAccessIT.java

should be:

myModule/src/test/java/ClientAccessIT.java

You could also update your pom file (if you really wanted tests to live in main) to include:

<build>
    <testSources>
        <testSource>
            <directory>src/main/test</directory>
        </testSource>
    </testSources>
</build>

It seems below jar is not available in your classpath. com.google.guava_1.6.0.jar

Download from the link below and add it to your classpath.

com.google.guava_1.6.0.jar

I used java print statements for easy understanding.

1. To check Element Present:

   if(driver.findElements(By.xpath("value")).size() != 0){
   System.out.println("Element is Present");
   }else{
   System.out.println("Element is Absent");
   }
   

   Or

   if(driver.findElement(By.xpath("value"))!= null){
   System.out.println("Element is Present");
   }else{
   System.out.println("Element is Absent");
   }
   

2. To check Visible:

   if( driver.findElement(By.cssSelector("a > font")).isDisplayed()){
   System.out.println("Element is Visible");
   }else{
   System.out.println("Element is InVisible");
   }
   

3. To check Enable:

   if( driver.findElement(By.cssSelector("a > font")).isEnabled()){
   System.out.println("Element is Enable");
   }else{
   System.out.println("Element is Disabled");
   }
   

4. To check text present

   if(driver.getPageSource().contains("Text to check")){
   System.out.println("Text is present");
   }else{
   System.out.println("Text is absent");
   }
   

Listeners are not automatically picked up until you have set them up using serviceloaders.

There are multiple ways to specify a listener, based on need.
If you do not want to apply them to all your tests, you may choose to apply a listener on a single class

eg.

@Listeners(Transformer.class)
public class InterceptorTC {

@Test(priority..

You can also specify a listener from maven surefire plugin. Read the using custom listener section here

Other ways to specify listener can be to define it in your suite xml and specify your suite xml file in the maven plugin.

.