How to use getHost method of org.testng.Interface ITestResult class

This is a valid doubt many testers have. Because the main() method is needed to run the Java program and while writing tests in TestNg we don't use main() method, and we use Annotations instead.

Annotations in TestNG are lines of code that can control how the method below them will be executed. So, in short you don't need to write main() method, TestNg do that by itself. Refer the code at the end in Annotations documentation to get the idea how it happens.

As rightly pointed out in this answer: https://stackoverflow.com/a/1918154/3619412

Annotations are meta-meta-objects which can be used to describe other meta-objects. Meta-objects are classes, fields and methods. Asking an object for its meta-object (e.g. anObj.getClass() ) is called introspection. The introspection can go further and we can ask a meta-object what are its annotations (e.g. aClass.getAnnotations). Introspection and annotations belong to what is called reflection and meta-programming.

Also, it's not necessary to have main() method in your tests, but you can use main() method to run the TestNg tests if you want. Refer this.

I met the same issue. cucumber-java 1.2.2 is working for me.

<dependency>
    <groupId>info.cukes</groupId>
    <artifactId>cucumber-java</artifactId>
    <version>1.2.2</version>
</dependency>

Thanks to M. Deinum. To solve my problem, I just replace the class AbstractTestNGSpringContextTests with AbstractTransactionalTestNGSpringContextTests.

package com.noahwm.hkapp.api;

import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.test.annotation.Rollback;
import org.springframework.test.context.ContextConfiguration;
import org.springframework.test.context.testng.AbstractTransactionalTestNGSpringContextTests;
import org.springframework.test.context.transaction.TransactionConfiguration;
import org.springframework.transaction.annotation.Propagation;
import org.springframework.transaction.annotation.Transactional;
import org.testng.Assert;
import org.testng.annotations.Test;

import com.noahwm.hkapp.api.db.dao.AppUserDao;
import com.noahwm.hkapp.api.db.model.AppUser;
import com.noahwm.hkapp.api.service.AppUserService;

@ContextConfiguration(locations = { "classpath:applicationContext-test.xml" })
public class AppUserServiceTestNGTest extends AbstractTransactionalTestNGSpringContextTests {

  @Autowired
  private AppUserService appUserService;

  @Test
  @Rollback
  @Transactional
  public void testApp() {
    AppUser appUser = new AppUser();
    appUser.setAge(10);
    appUser.setGender("F");
    appUser.setMobilePhone("13219201034");
    appUser.setName("HKAPP Test");
    appUserService.createUser(appUser);
    String appUserId = appUser.getId();
    Assert.assertNotNull(appUserId);
  }
}

I would do something like this:

WebDriverWait wait = new WebDriverWait(driver, 50);

try {
    wait.until(ExpectedConditions.visibilityOfElementLocated(By.xpath("//*[contains(text(),'" + "Your Report is complete" + "')]")));
    // If you get here, the condition did not timeout and so the
    // report was generated.
    log.info("Your report was generated.");
}
catch (TimeoutException ex) {
    // Timed out, the report was not generated.
    log.error("Your report was not generated.");
    throw ex;
}
finally {
    driver.close();
    // change focus back to old tab
    driver.switchTo().window(oldTab);
    Thread.sleep(3000);
}

If you must generate an AssertionError you could always do this in the catch clause:

catch (TimeoutException ex) {
    // Timed out, the report was not generated.
    log.error("Your report was not generated.");
    Assert.assertTrue(false);
}

Standard list, maybe not, but you have some examples:

syntax: regexp

\.*py[co]
\.DS_Store
~$
\.coverage
\.egg-info

syntax: glob

nbproject
app.yaml
auth.py
dist
target
WEB-INF/appengine-generated

Basically, at least any directory with generated content should be ignored.

The same principles holds true for Java app projects like this one or that one:

syntax: glob

*~
*.patch
*.sedbak
*/target/*
*/<project_name>searchindex/*
*/test-output/*

hs_err_pid*.log
tomcat

syntax: regexp
\.jar$

^\.pc/
^.ant-targets-build.xml
\.pages.xml.spdia$
temp-testng-customsuite.xml$

# eclipse and maven stuff
^target

# kde related
\.directory$

#gwt related
^<project_name>-war/war/WEB-INF/classes/
^<project_name>-war/tomcat
\.gwt-tmp$
^<project_name>-war/org.fedorahosted.<project_name>.webtrans.Application
^<project_name>-war/war/org.fedorahosted.<project_name>.webtrans.Application

Off course, I will keep any Eclipse or maven related file under source control, in order to facilitate the build step when anyone will clone the repo.

AFAIK, there is no direct way of excluding configuration methods from the testng-results.xml file.

But all said and done, the current entries in the testng-results.xml still lets you distinguish a configuration method from a test method.

For a configuration method there's an extra attribute named is-config="true".

See below for excerpts from your own xml file

<test-method 
    status="PASS" 
    signature="beforeMethod()[pri:0, instance:com.my.test.MyTest@3567135c]" 
    name="beforeMethod" 
    is-config="true" 
    duration-ms="4" 
    started-at="2018-01-22T16:47:46Z" 
    finished-at="2018-01-22T16:47:46Z">
    <reporter-output>
    </reporter-output>
</test-method> <!-- beforeMethod -->

But for a regular @Test method, the attribute is-config=true would not be available.

See below :

<test-method 
    status="PASS" 
    signature="test1()[pri:0, instance:com.my.test.MyTest@3567135c]" 
    name="test1" 
    duration-ms="0" 
    started-at="2018-01-22T16:47:46Z" 
    finished-at="2018-01-22T16:47:46Z">
    <reporter-output>
    </reporter-output>
</test-method> <!-- test1 -->

Would that not help you with your downstream xml processing ?

If that still doesn't work for you, then the other alternatives would include:

• you would build your own version of org.testng.IReporter implementation wherein you construct this xml and then wire it in as a listener.
• You create a package called org.testng.reporters wherein you duplicate the contents of the class org.testng.reporters.XMLReporter into this package, alter the method org.testng.reporters.XMLSuiteResultWriter#getTestResultAttributes to add extra attributes to the method if its not a @Test method.

I had the same problem using IntelliJ and that's how I fixed it:

Select Use default reporters under the Listeners tab on the Run/Debug Configurations

PS: Remember to add the path for the testng xml file under the Suite field

You can inject a ITestResult into an @AfterMethod and get the time result from there:

List<Long> timeResults = ...

@AfterMethod
public void afterMethod(ITestResult result) {
  timeResults.add(result.getEndMillis() - result.getStartMillis()) 
}

You could take a look at Junit Theories (introduction)

import org.junit.experimental.theories.DataPoints;
import org.junit.experimental.theories.Theories;
import org.junit.experimental.theories.Theory;
import org.junit.runner.RunWith;

import static org.junit.Assert.assertTrue;

@RunWith(Theories.class)
public class AdditionWithTheoriesTest {

  @DataPoints
  public static int[] positiveIntegers() {
       return new int[]{
                        1, 10, 1234567};
  }

  @Theory
  public void a_plus_b_is_greater_than_a_and_greater_than_b(Integer a, Integer b) {
      assertTrue(a + b > a);
      assertTrue(a + b > b);
  }
}

This way you can pass parameters to a test. In your method annotated with DataPoints you'll need to fetch all the excell data and return it.