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

Go to Project --> Clean

It works for me

Your test ckass needs to extend AbstractTestNGSpringContextTests. Or if your code is testing database acces another useful class to extend is AbstractTransactionalTestNGSpringContextTests.

Hinted by this Chromedriver ticket (about the silent option), I looked in the source of ChromeDriverService.java, and found a reference to "webdriver.chrome.logfile".

After adding -Dwebdriver.chrome.logfile="/dev/null" to my java command, the logs became readable again: The usless ChromeDriver logs were gone, while theSystem.out.println calls and exceptions are still shown in the console.

I start java with the following parameters (Linux / Mac):

DIR=path/to/dir/containing/selenium/and/stuff
cd "$DIR" && java -cp "$DIR\
:$DIR/output\
:$DIR/bin/selenium-server-standalone-2.33.0.jar" \
-Dwebdriver.chrome.driver="$DIR/bin/chromedriver" \
-Dwebdriver.chrome.args="--disable-logging" \
-Dwebdriver.chrome.logfile="/dev/null" \
AllTests

If you're on Windows:

set DIR=path\to\dir\containing\selenium\and\stuff
cd "%DIR%" && java -cp "%DIR%;%DIR%\output;%DIR%\bin\selenium-server-standalone-2.33.0.jar" ^
-Dwebdriver.chrome.driver="%DIR%\bin\chromedriver.exe" ^
-Dwebdriver.chrome.args="--disable-logging" ^
-Dwebdriver.chrome.logfile=NUL ^
AllTests

Explanation for the composition of my classpath (-cp): My tests are located in a directory at "$DIR/output". The Selenium jar file is placed in "$DIR/bin/selenium-server-standalone-2.33.0.jar". "AllTests" is the name of my class containing public static void main(String[] args) - this launches my tests.

The other parameters are self-explanatory, adjust it to your needs. For convenience (used in a shell/batch script), I've declared the common directory in a variable DIR.

Just remove String uid, String pid in main method and run once again as

public void verifyLogin(String uid, String pid)

to

public void verifyLogin()

even though the javadocs say onFinish of IsuiteListener should execute once per all the suites run but i saw it getting executed multiple times. so i used IExecutionListener. below is the code i used.

public class MyReporter implements IExecutionListener {


@Override
public void onExecutionStart() {

}

@Override
public void onExecutionFinish() {

    ReportDownloadUtil.downloadReport();
}



}

Indeed you will need a custom converter for this as it is two nested collection which you do not want to show and those objects might have other child elements which would be serialized.

This is a case not directly covered by XStream, but easily fixed with a custom converter.

You can find all this in a git clone of your project which contains all those modifications. But as everything should be visible here, I subsequently explain the key portions to the question including some code examples.

I implemented such a converter for your project. The code doing the conversion is this:

  @Override
  public void marshal(Object source, HierarchicalStreamWriter writer, MarshallingContext context) {
    TestRow test = (TestRow)source;
    for (TestArguments arg : test.getArguments()) {
      for (ArgObject val : arg.getAllTestArguments()) {
        writer.startNode(val.getKey());
        writer.addAttribute("type", val.getType());
        writer.setValue(val.getVal());
        writer.endNode();

      }
    }
  }

  @Override
  public Object unmarshal(HierarchicalStreamReader reader, UnmarshallingContext context) {
    TestArguments testargs = new TestArguments();
    while (reader.hasMoreChildren()) {
      reader.moveDown();
      String typeval = reader.getAttribute("type");
      if (typeval.isEmpty()) {
        typeval = "null";
      }
      testargs.getAllTestArguments().add(new ArgObject(reader.getNodeName(), typeval, reader.getValue()));
      reader.moveUp();
    }
    TestRow result = new TestRow(testargs);
    return result;
  }

This will serialize all ArgObjects to xml with the flat node structure you defined in your ArgConverter. The deserialization creates the object back from this data.

You had two bugs in your source code which prevented deserialization:

• XStream deserialization does not recognize all alias Annotations. It had problems with your root element SuiteData (aliased to suite). For this I added a aliad to the XStream object like this xStream.alias("suite", SuiteData.class); in your XMLDataHelper.
• If you create a TestArguments instance with a default constructor (as you'll have to through deserialization), you call reset which assigns your argsWrapper member to null which then makes adding arguments quite impossible. I fixed that be newly initializing that member variable in the reset method (argsWrapper = new ArrayList<ArgObject>();).

As far as I understand your code this works as expected for serialization / deserialization. I wrote a small test program to force this process in each way and it seems to produce the same result:

public class XMLDataHelperTest {

  public static void main(String[] args) {
    File file = new File(System.getProperty("user.dir"), "test.xml");
    if (file.isFile()) {
      assertTrue(file.delete());
    }

    // write it once
    XMLDataHelper helper = new XMLDataHelper(file.getAbsolutePath());

    // read it once
    helper = new XMLDataHelper(file.getAbsolutePath());
    System.out.println(file);
  }
}

Well the first case uses the Assert class from your testing framework and is the right way to go, since TestNG will report the error in an intelligent way.

You can also add your own message to the test:

Assert.assertNotNull(object, "This object should not be null");

The second case uses the assert keyword - it will give you a failure but the stack trace may or may not be understandable at a glance. You also need to be aware that assertions may NOT be enabled.

After a long long time, I found the solution to my problem.. It all goes away, by adding in the suite tag, the entryconfigfailurepolicy, and set it to continue, in your suite xml files like this:

    <suite name="Test-Suite" configfailurepolicy="continue">

By default the value of the parameter was skip, which was causing tests to skip, if a failed configuration occured.

Probably this is a bit late, but your driver object is not being shared by firsttest and secondtest. Each of them have their own copies. So, whatever gets initialized is one's own copy. Whichever class would run first would work and the second class would not have it since it's copy is not initialized. What you can do is to have a class which returns the same driver object when asked for it..

public class DriverInitializer {

private static WebDriver driver;

@BeforeSuite
public void setTestSuite() throws MalformedURLException {
    driver = new FirefoxDriver();
}

@AfterSuite
public void endTestSuite() {
    driver.quit();
}

public static WebDriver getDriver(){
    return driver;
}

}

Then have all cases call eg. firstTest calls

DriverInitializer.getDriver().get("http://www.google.com");

Secondtest calls

DriverInitializer.getDriver().get("http://cnn.com");

So no matter who's calling the same driver instance would be returned.

The beforesuite and aftersuite need to be defined only once , they could be placed anywhere.just that in the above example they are referring to a private variable and hence i had to keep them in there..