How to use Interface IDynamicGraph class of org.testng package

If you're using JUnit, first of all "parallel" applies only to TestNG, and so do a few other attributes, so they won't be of help / interest to you:

• http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html

Here's what works for us in a JUnit setup (doesn't work well for TestNG as just posted here: Running test in parallel with surefire and displaying them properly with the TestNG Jenkins plugin):

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <configuration>
    <reuseForks>false</reuseForks>
    <forkCount>2.5C</forkCount>
  </configuration>
</plugin>

So I think you need to increase your forkCount (with forkCount = 1.0 you won't get parallel stuff going).

For reference, here's a bit more about the small print when it comes to running tests in parallel (incl. forkCount explanation and examples):

• http://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html

Allure 2 listeners are managed by SPI mechanism. So there're several steps you need to do to make it works:

• Implement StepLifecycleListener interface and override required methods.
• Create META-INF/services folders in your project's resources root.
• Create a new file by the full name of this interface in the above folder.
• Add the full path to your implementation class into this file.

You can find an example in the the following project: https://github.com/sskorol/allure2-testng-report/blob/master/src/test/resources/META-INF/services/io.qameta.allure.listener.StepLifecycleListener

More info about SPI: http://docs.oracle.com/javase/tutorial/sound/SPI-intro.html

I pushed extension bit further, it can be found on maven central and there is part of help written + tests to look how it should be done.

I also created "generic" deployer builder that should work with javaee6.

https://github.com/ingwarsw/arquillian-suite-extension

You can get a list of all running threads (Get a List of all Threads currently running in Java):

Set<Thread> threadSet = Thread.getAllStackTraces().keySet();

Then you can iterate through the list in some test that you write calling Thread.isDaemon(). You'll probably need to throw out some threads that correspond to the JVM or the JUnit framework, but that's probably doable by checking other aspects of the threads, like their name.

Try setting an implicit wait of maybe 10 seconds.

gmail.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);

Or set an explicit wait. An explicit waits is code you define to wait for a certain condition to occur before proceeding further in the code. In your case, it is the visibility of the password input field. (Thanks to ainlolcat's comment)

WebDriver gmail= new ChromeDriver();
gmail.get("https://www.gmail.co.in"); 
gmail.findElement(By.id("Email")).sendKeys("abcd");
gmail.findElement(By.id("next")).click();
WebDriverWait wait = new WebDriverWait(gmail, 10);
WebElement element = wait.until(
ExpectedConditions.visibilityOfElementLocated(By.id("Passwd")));
gmail.findElement(By.id("Passwd")).sendKeys("xyz");

Explanation: The reason selenium can't find the element is because the id of the password input field is initially Passwd-hidden. After you click on the "Next" button, Google first verifies the email address entered and then shows the password input field (by changing the id from Passwd-hidden to Passwd). So, when the password field is still hidden (i.e. Google is still verifying the email id), your webdriver starts searching for the password input field with id Passwd which is still hidden. And hence, an exception is thrown.

Out of the box a new Selenium WebDriver instance uses an empty profile, unless you specify otherwise.

Sounds like you are using the same user for both test runs. When the users log-out or in it gets the same session state as in all other locations. Thus it is again on the same page or logged-out. I would ask the developers to explain how the session management works for your application.

Test insolation:

You will need to isolate the test-data and or test-environment for each parallel run. You could start with creating a new user for your test before you start the test.

See this answer for more idea's how to isolate tests from each other: https://sqa.stackexchange.com/a/25623/3201

Other reads:

• Not testing in Isolation Anti-Pattern: https://sqa.stackexchange.com/questions/8508/what-are-anti-patterns-in-test-automation/8516#8516

i think, you need to upgrade maven-surefire-plugin version to 2.19.1, if you are properly create suiteXmlFile. and need to specify the actual path of suiteXmlFile, for Example : <suiteXmlFile>src/test/resources/testng.xml</suiteXmlFile>. and if you want to use <suiteXmlFile>${suiteXmlFile}</suiteXmlFile>, you need to run mvn clean install test -DsuiteXmlFile=testngSuite.xml. for more you can refer bellow links(maven-surefire-plugin document):

http://maven.apache.org/surefire/maven-surefire-plugin/examples/testng.html

http://www.seleniumeasy.com/maven-tutorials/how-to-execute-selenium-webdriver-testng-xml-using-maven

While you are already using QAF you already have solutions available for such use case. First of all you should use Locator repository, Instead of hard-coding locator in page just provide locator key.

For example:

In page.loc File

my.ele.locator=<locatorStretegy>=<locator>
my.ele.locator=name=elemName

In Page class:

@FindBy(locator = "my.ele.loc")
private QAFWebElement btnSomeElement; Now coming to your problem, if most of the locator very with environment then you can utilize

resource management capabilities of QAF. In other case you can use alternate locator strategy provided by QAF. For example:

my.ele.locator=['css=.cls#eleid','name=eleName','name=eleName2']
my.ele.locator=['name=eleNameEnv1','name=eleNameEnv2']

I think a good solution for your problem can be using group like this:

import org.testng.Assert;
import org.testng.annotations.Test;

public class GroupTestExample {
   String message = ".com";
   MessageUtil messageUtil = new MessageUtil(message);

   @Test(groups = { "functest", "checkintest" })
   public void testPrintMessage() {
      System.out.println("Inside testPrintMessage()");
      message = ".com";
      Assert.assertEquals(message, messageUtil.printMessage());
   }


   @Test(groups = { "checkintest" })
   public void testSalutationMessage() {
      System.out.println("Inside testSalutationMessage()");
      message = "tutorialspoint" + ".com";
      Assert.assertEquals(message, messageUtil.salutationMessage());
   }


   @Test(groups = { "functest" })
   public void testingExitMessage() {
      System.out.println("Inside testExitMessage()");
      message = "www." + "tutorialspoint"+".com";
      Assert.assertEquals(message, messageUtil.exitMessage());
   }  
}

and your xml file would be like this:

<?xml version = "1.0" encoding = "UTF-8"?>
<!DOCTYPE suite SYSTEM "http://testng.org/testng-1.0.dtd" >

<suite name = "Suite1">
   <test name = "test1">

      <groups>
         <run>
            <include name = "functest" />
         </run>
      </groups>

      <classes>
         <class name = "GroupTestExample" />
      </classes>

   </test>
</suite>