How to use getStatus method of org.testng.reporters.XMLReporterConfig class

Aditya,

Your code(testng.xml) for running parallel test on different-different or same system should be like below:

Testng.xml

 <!DOCTYPE suite SYSTEM "Http://testng.org/testng-1.0.dtd">
    <suite name="My Sample Suite" verbose="3"  parallel="tests" thread-count="2">   


      <test name="Run on Firefox">
        <parameter name="mybrowser"  value="firefox"/>
        <parameter name="myip"  value="http://172.16.10.119:5566/wd/hub"/>
        <classes>
          <class name="testcases.Login"/>
        </classes>
     </test>  
    <test name="Run on Chrome">
        <parameter name="mybrowser"  value="chrome"/>
        <parameter name="myip"  value="http://172.16.10.106:5567/wd/hub"/>
        <classes>
          <class name="testcases.Login"/>
        </classes>
     </test> 
     </suite>

here i am trying to acess one linux(ttp://172.16.10.119:5566) and one mac(http://172.16.10.106:5567) and sending its ip and browser as a parameter. To run it parallel i have mentioned in my <testsuite> tag as parallel="tests" thread-count="2"

I hope that you are pretty clear now.

Realizing that writing a test is hard, often means that the code can be improved. And to me, that's one of the biggest reason to write tests: They force you to write better code!

If you look at your code snippet, it actually does several things:

• It gets the version system property, possibly throwing an exception
• It extracts the two versions and converts to integers
• Then it compares them

When considering that, you see that this can be split into several functions. And they can be tested more easily.

public static boolean verifyJavaVersion() throws UserException {
    String javaVersion = ...
    int installedJavaVersion = extractJavaVersion(javaVersion);
    int installedJavaReleaseVersion = extractJavaReleaseVersion(javaVersion);
    checkVersion(installedJavaVersion, REQUIRED_JAVA_VERSION, installedJavaReleaseVersion, MINIMUM_JAVA_RELEASE_VERSION);
}

each of these should be easy to test.

I removed your null check for simplicity, but you see the idea.

Try extending XmlTest in your test class and call setName(). I extended XmlSuite and used setName to name my "test suite" which is a class with multiple tests defined in it and that worked for me. In fact I just tried what I suggested on the same class and now it's called a test with the correct name. I'm not sure why the ITest interface is being ignored as I also tried that approach without success.

Additionally, until this issue is fixed, if things still aren't working for you after following the previous advice OR you do not wish your code to be executed before every single method, then add the following code to your test class:

@Override
@BeforeSuite
protected void springTestContextPrepareTestInstance() throws Exception {
    super.springTestContextPrepareTestInstance();
}

This ensures that the Spring Context will be prepared before your @BeforeClass methods are executed.

*note, I posted this answer since in the title you're asking about @BeforeClass, even though there is no usage of @BeforeClass in your sample code.

First of all you have String[] args. It's array of passed parameters. So if you're running:

java -jar your_jar.jar param1 param2

you automatically obtain args[0]="param1" and args[1]="param2"

You also can use a system properties.

Running

java -jar your_jar.jar -Dparam1=12 -Dparam2=13

You can call System.getProperty("param1") from anywhere and it will return you "12".

And... Imho the best way to run TestNG project programmaticaly is using of maven/gradle surefire plugin.

The problem is that your getDriver method is static.

Solution #1: Make method non-static (this will either need to make the driver variable non-static as well, or use return Browser.getDriver(); )

public WebDriver getDriver() {
    return driver;
}

Or, call the getDriver method by using Browser.getDriver

WebElement query = Browser.getDriver().findElement(By.name("q"));

Override the toString() method in your pojo class like below

@Override
public String toString() {
    return "brand: " + this.brand + ",color: " + this.color;
}


car1.toString().equals(car2.toString()); //It will return true if both objects has same values

In case you have large nos of parameter i will suggest you to go with bellow code

public static boolean comparePOJO(Object obj1, Object obj2) {
    return new Gson().toJson(obj1).equals(new Gson().toJson(obj2));
}
comparePOJO(car1,car2); //It will return true

Usually this information is provided in TestNG report.

If you need this time while running test suite, in @AfterMethod use ITestResult object:

@AfterMethod
public void getRunTime(ITestResult tr) {
    long time = tr.getEndMillis() - tr.getStartMillis();
}

---

Related: TestNG Dependency injection

So...

Your prerequisites:

• excel file, each row - one dataset
• run test for each dataset

What can you do:

1. Create @DataProvider which return Iterator<Object[]> with your datasets where each Object[] is your row from excel. (the easiest one)
2. Use @Factory to manually iterate through your datasets and call test methods.
3. Use @DataProvider to provide data for @Factory and do as above. The 2nd and 3rd options are complicated, but have some benefits if you has other parameters, except datasets, to run tests.