How to use GroupPanel class of org.testng.reporters.jq package

UPDATE:

My new setup uses a different plugin that supports parallel execution of scenarios, better reporting, and is still actively maintained:

build.gradle

plugins {
  ...
  id "com.commercehub.cucumber-jvm" version "0.11"
}

addCucumberSuite 'cucumberTest'

dependencies {
  ...
  cucumberTestCompile 'info.cukes:cucumber-java:1.2.5'  // or -java8 if you prefer lambda notation

}

directory structure:

└── src
    ├── cucumberTest
    │   ├── java
    │   │   └── package1 
    │           └──       <- Glue
    │   └── resources    
    │       └── package2 
    │           └──       <- Features
    ├── main
    │   └── java
    └── test
        └── java

package1 and package2 names (together with many other options) can be specified in the build.gradle file

OLD

My previous setup for using cucumber for java with gradle.

build.gradle

plugins {
    id "java"
    id "com.github.samueltbrown.cucumber" version "0.9"
  }   

dependencies {
    cucumberCompile 'info.cukes:cucumber-java:1.2.4'
}

cucumber {
    formats = ['pretty','junit:build/cucumber.xml']
}

Directory layout

└── src
    ├── cucumber
    │   ├── java         <- Glue
    │   └── resources    <- Features
    └── main
    │    └── java
    └── test
        └── java

Command

gradle cucumber

With testng, you can annotate your test method like this :

@Test(expectedExceptions = IllegalStateException.class, 
      expectedExceptionsMessageRegExp = "...")
public void your_test() {
  [...]
}

There are two problems to solve here. Firstly, we need some code that will take a screenshot and secondly, we need to get that code to run when a test fails.

Taking a screenshot is pretty easy in Selenium using the TakesScreenshot interface. So you'll need something like:

TakesScreenshot ts = (TakesScreenshot)driver;
byte[] image = ts.getScreenshotAs(OutputType.BYTES);

try {
  File screenshot = new File("/some/path/myscreenshot.png");
  FileOutputStream fos = new FileOutputStream(screenshot);
  fos.write(image);
  fos.close();
} catch (IOException ex) {
  fail("Failed to write screenshot");
}

Depending on the driver you're using you might need to use the Augmenter class too.

Running code when tests fail is going to depend on the test framework you use, not on Selenium. For example, if you're using TestNG you can write an instance of ITestListener to listen to the results of your tests and take a screenshot when one fails.

Just Add (alwaysRun = true) to the @BeforeClass annotation.

So your fundamental class should look like -:

public class FundamentalTest {

protected BasePage basePage;

@BeforeClass(alwaysRun = true)
@Parameters({ "testServer" })
public void init(String testServer) {
    basePage = PageFactory.initElements(new FirefoxDriver(), BasePage.class);
    basePage.driver.manage().timeouts().implicitlyWait(10000, TimeUnit.MILLISECONDS);
    basePage.driver.get(testServer);
}

@AfterClass
public void destruct() throws InterruptedException {
    Thread.sleep(5000);
    basePage.driver.close();
}

}

Thanks alot,this worked for me

The parallelization in TestNG depends on the mode specified in your suite.

<suite name="My suite" parallel="methods" thread-count="5">

Will make 5 methods at the same time run in paralell, as long as they don't depend on each other. Dependend methods will wait until all dependencies has been runned before they are started. Other modes are "tests", "classes" and "instances".

If you want different threading for different tests inside the same xml you can add the parellel property to the test tag instead e.g.

<suite name="default" thread-count="4">
    <test name="asa" parallel="methods">
        <classes>
            <class name="multiThreaded"/>
            <class name="multiThreaded"/>
        </classes>
    </test>
    <test name="asa" parallel="false">
        <classes>
            <class name="singleThreaded"/>
            <class name="singleThreaded"/>
        </classes>
    </test>
</suite>

See http://testng.org/doc/documentation-main.html#parallel-tests for more information

The simplest way is by using ITestResult.

    @Override
    public void afterInvocation(IInvokedMethod arg, ITestResult arg1) { 
      System.out.println(arg.getTestMethod().getMethodName());
      System.out.println(arg1.getMethod().getDescription());
    }

The second sysout will return a (String) description of the invoked test method.

Sounds like you need to add the TestNG tasks to Ant. It doesn't know what class to run when it encounters the <testng> tag.

Though it's syntactically not incorrect. But you should preferably rephrase your tests to use expectedException instead and be specific about the exception is thrown as well. For e.g. :

If your method fromTest() when called with "test" as an argument could throw an NumberFormatException, then your test definition for such behaviour should be :

@Test(expectedExceptions = NumberFormatException.class)
public void testMethod() {
    System.out.println("About to throw an exception!");
    fromTest("test");
}

Note: If you believe that the exception may so happen within your test execution itself instead of any other method being called from it. I would suggest to not catch it. Let it fail and then you shall fix it.

What I think is happening here is that my browser is set to use a specific proxy to connect to the Internet. my Java program (my test, in this case) does not automatically use that proxy, so i need to tell it to do so explicitly.

@BeforeClass
public void setProxy() 
{
System.setProperty("http.proxyHost", YOUR_PROXY_HOST_HERE);
System.setProperty("http.proxyPort", YOUR_PROXY_PORT_HERE);
}