How to use addInterceptors method of org.testng.DataProviderHolder class

The surprise: Eclipse, understood automatically even if there are duplicate jars and was able to run the test scripts. However, ANT could not do that. So, I removed the jar com.google.common, which made me to run the test scripts from command line.

Lesson learnt: Do not have duplicate .jar files.

TestNG is something you have a look at. I have used it. Provides a lot of features that JUnit provides.

This page has advantages of TestNG Over Junit.

I see a signature in testNG taking an actual exception:

http://testng.org/javadoc/org/testng/Assert.html#fail(java.lang.String,%20java.lang.Throwable)

And also fail throws a runtime exception (TestNGException), so you can launch that exception yourself and the test harness will understand.

There are 2 most popular frameworks for unit tests: JUnit and TestNG. Both are annotation based. To create test you have to create class and mark each method that performs test using annotation @Test.

JUnit is older and have more extensions (DBUnit, Cactus etc). TestNG has much more annotations. Very important feature of TestNG is ability to create test groups using annotations.

Yet another group of tools you will probably need is mocking tools (EasyMock, EasyMock etc.)

You are catching NoSuchElementException and inside the catch block you are checking if it is a NoSuchElementException which does not add any value. You are testing if JDK works correctly.

To check if the element does not exist on page, you could use a method like this :

public boolean isElementPresent(By locatorKey) {
    try {
          driver.findElement(locatorKey);
          return true;
        } catch (org.openqa.selenium.NoSuchElementException e) {
          return false;
        }
}

You should then assert on the above method,

if element should not be present

Assert.assertFalse(isElementPresent(By.id("login")));

if element should be present

Assert.assertTrue(isElementPresent(By.id("login")));

TestNG will run all the public methods from a class with a @Test annotation. Maybe you could change the methods you don't want TestNG to run to be non-public

Take a look at the dependency injection section in the documentation. It states that dependency injection can be used for example in this case:

Any @BeforeMethod (and @AfterMethod) can declare a parameter of type java.lang.reflect.Method. This parameter will receive the test method that will be called once this @BeforeMethod finishes (or after the method as run for @AfterMethod).

So basically you just have to declare a parameter of type java.lang.reflect.Method in your @BeforeMethod and you will have access to the name of the following test name. Something like:

@BeforeMethod
protected void startTest(Method method) throws Exception {
    String testName = method.getName(); 
    System.out.println("Executing test: " + testName);
}

There's also a way by using the ITestNGMethod interface (documentation), but as I'm not exactly sure on how to use it, I'll just let you have a look at it if you're interested.

I had the same issue and it was only because of the Rule, you can set the activity to launch in rule's constructor:

@Rule
public ActivityTestRule<MainActivity> menuActivityTestRule = 
        new ActivityTestRule<>(MainActivity.class, true, true);

last argument is responsible for launching the activity.

This error message...

An internal error occurred during: "Launching NewTest"
org.testng.eclipse.maven.MavenTestNGLaunchConfigurationProvider.getClasspath(Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/util/List;

...implies that there was incompatibility between TestNG and Maven related classfiles.

Historically, this error would occur if while installing testng you have kept the checkbox for M2E Maven as checked.

The easiest approach to address this issue would be to reinstall the TestNG ensuring that the checkbox for M2E Maven is kept unchecked.