How to use JUnitTestFinder class of org.testng.junit package

1. You don't need to create a separate test project, but you can if you want to. Most people do it by creating a separate test folder in the same project. Whether you have a separate test project or just a test folder, you should replicate your package structure inside your test folder, so that each test class is testing an application class in the same package.
2. Yes. Mockito is designed to be used with JUnit, or with some other testing framework, such as TestNG. Most people use it with JUnit. Most of the examples on the Mockito web site use JUnit. So, yes, you'll need the JUnit libraries, or the libraries for whatever other testing framework you choose.
3. A Mockito test is a JUnit test (or a TestNG test, or whatever). So there's no "far more easier to run", as you put it. Just write a JUnit test that uses Mockito, and run it in the same way as any other JUnit test.
4. Start with the Mockito web site and Mockito repository.

I have faced the same problem while I was working with raspbian OS for raspberry pi. The problem was the java project was referencing to one of my previous project.

I resolved this problem by doing following steps.

1. Go to Project->properties
2. In properties window's left pane select "Run/Debug Settings".
3. Select "Configure" and click "edit"
4. In tab "Main" replace Project to your current project.
5. Select "Main class" by clicking on search button(it will be your class name).
6. Now hit OK.

1. They are tools to help you organize your tests. You can define what you want to run before/after tests, you can group your tests, and reporting on them is made easier.

2. It is usually mentioned with Selenium because Selenium is a common testing tool. The two work together well, but they are completely separate. (Selenium connects you to your browser, TestNG/JUnit organizes the tests)

3. Yes. You should be able to pick them up. They are designed to be fairly easy to learn.

1) IMethodInterceptor allows user to modify the list of methods (or Test) to be executed. 2) IInvokedMethodListener allows user to perform certain action before/after a method has been executed. something like clean up or setup. 3) First IMethodInterceptor is called so that if user wishes to modify the list of method to be executed then a user can change it and pass it to TestRunner. Please see below example code:

    package practise;

import org.testng.IInvokedMethod;
import org.testng.IInvokedMethodListener2;
import org.testng.ITestContext;
import org.testng.ITestResult;

public class InvokedMethodListener implements IInvokedMethodListener2
{
    @Override
    public void afterInvocation(IInvokedMethod arg0, ITestResult arg1)
    {
        System.out.println(Thread.currentThread().getStackTrace()[0].getMethodName());
    }

    @Override
    public void beforeInvocation(IInvokedMethod arg0, ITestResult arg1)
    {
        System.out.println(Thread.currentThread().getStackTrace()[0].getMethodName());
    }

    @Override
    public void afterInvocation(IInvokedMethod arg0, ITestResult arg1, ITestContext arg2)
    {
        System.out.println(Thread.currentThread().getStackTrace()[1].getMethodName());
    }

    @Override
    public void beforeInvocation(IInvokedMethod arg0, ITestResult arg1, ITestContext arg2)
    {
        System.out.println(Thread.currentThread().getStackTrace()[1].getMethodName());
    }

}


    package practise;

import java.util.List;

import org.testng.IMethodInstance;
import org.testng.IMethodInterceptor;
import org.testng.ITestContext;

public class MethodInterceptor implements IMethodInterceptor
{

    @Override
    public List<IMethodInstance> intercept(List<IMethodInstance> arg0, ITestContext arg1)
    {
        System.out.println(Thread.currentThread().getStackTrace()[1].getMethodName());
        return arg0;
    }

}

    package practise;

import org.testng.annotations.Listeners;

@Listeners(value={MethodInterceptor.class,InvokedMethodListener.class})
public class Test
{
    @org.testng.annotations.Test
    public void first()
    {
        System.out.println(Thread.currentThread().getStackTrace()[1].getMethodName());
    }

    @org.testng.annotations.Test
    public void second()
    {
        System.out.println(Thread.currentThread().getStackTrace()[1].getMethodName());
    }
}

A couple of ideas:

Even if you are running the tests programmatically, you should be able to invoke TestNG on a testng.xml file. Add parameters to the file like so (from the documentation):

<suite name="My suite">
   <parameter name="parameter"  value="Foo"/>
   <test name="Courier Test" />
   < ... >

If for some reason you aren't using a testng.xml file, you can use a DataProvider, either as a method within the test class or as a static class, depending on what you need to do. Examples below (also from the documentation).

DataProvider inside the class:

//This method will provide data to any test method that declares
//that its Data Provider is named "test1"
@DataProvider(name = "test1")
public Object[][] createData1() {
   return new Object[][] {
     new Object[] { "Parameter" }
   }
}

//This test method declares that its data should be supplied 
//by the Data Providernamed "test1"
@Test(dataProvider = "test1")
public void Courier_Test(String parameter) {
 System.out.println(parameter);
} 

DataProvider in external class:

public static class StaticProvider {
  @DataProvider(name = "create")
  public static Object[][] createData() {
    return new Object[][] {
      new Object[] { "Parameter" }
    }
  }
}

public class Courier {
  @Test(dataProvider = "create", dataProviderClass = StaticProvider.class)
  public void Courier_Test(String parameter) {
    // ...
  }
}

Question : The @test method will run for each row from the excel sheet when I use data provider?

Ans : Yes, it will run for each set of data. It depends on you how you read data from excel file.

Take this as an example :

@DataProvider(name = "test1")
public Object[][] createData1() {
 return new Object[][] {
   { "Cedric", new Integer(36) },
   { "Anne", new Integer(37)},
 };

@Test(dataProvider = "test1")
public void verifyData1(String n1, Integer n2) {
 System.out.println(n1 + " " + n2);
}

The verifyData1 method will be running two times irrespective of any set of data, irrespective of whether first one failed or not.

Q : What happens when one of the row failed to process?
Ans : Test case would be failed for that particular row , and execution will continue by reading the next set of data from excel.

Q. Does it run the rest of the rows after this failure?
Ans : Ideally it should , now again it depends whether you have @AfterMethod with you or not.

Q. Do I have to re-initiate the selenium webdriver and login method again when it fails?

Ans : No. It's better if you are initializing driver in @BeforeMethod , because before method would be running prior to each set of data which is generated by dataprovider.

Hope this will help.

The problem is a dependency issue. In my pom.xml I had a dependency on some classes which itself depended on TestNG 5.11. This worked pretty good until I figured out that I was not able to use the @Listeners annotation.

With the command

mvn dependency:tree

I was able to figure out that I had the wrong dependencies. To get rid of them I had to change the pom.xml around the artifact dependent on TestNG 5.11:

<dependency>
    <groupId>some.group.id</groupId>
    <artifactId>the.artifact.id</artifactId>
    <vers‌​ion>1.0</version>
    <exclusions>
        <exclusion>
            <groupId>org.testng</groupId>
            <artifactId>‌​testng</artifactId>
        </exclusion>
    </exclusions>
</dependency>

After that the correct TestNG dependency was working fine and I was able to use my Listener.

On a side note: The behavior of when e.g. retryAnalyzers and Listeners are called changed dramatically over the versions from 5.11 to 6.9.6, and I guess it did so quite a few times. There are for example many questions on STO dealing with "how to fix reports for retried tests which eventually pass" - none of those approaches I found worked fine for me, so I figured out one myself. This is not exactly related to the problem, but I just want you to make sure that you double check if your listeners and analyzers are called as expected and work as intended after fixing the dependencies.

I am currently trying to do the same. I found the following maybe that helps you:

http://testng.org/doc/documentation-main.html#methodinterceptors

If I get some sort of solution for my problem I could add some of my code here if you want.

EDIT

I am checking for 2 Kinds of TestClasses that should be executed in the order 1 2 1 2 1 2 not 1 1 1 2 2 2 as done by TestNG

public class ExampleInterceptor implements IMethodInterceptor {

@Override
public List<IMethodInstance> intercept(List<IMethodInstance> paramList, ITestContext paramITestContext) {

     //You have to watch out to get the right test if you have other tests in oyur suite        
    if (!paramITestContext.getName().equals("UnwantedTest")) {
        for (IMethodInstance iMethodInstance : paramList) {
            Object[] obj = iMethodInstance.getInstances();
            if (obj[0] instanceof Class1) {
                //DO your stuff like putting it in a list/array
            } else {
                //DO your stuff like putting it in a list/array with the other Testclasses
            }
        }
    }
    List<IMethodInstance> result = new ArrayList<IMethodInstance>();

            //Put the results in the results

    }
    return result;
}

}

Hope that helps. If you got questions ask.

The reason for this problem is related to the selenium version in "pom.xml". You can edit version to 3.141.59. your pom.xml file code updating:

<dependency>
    <groupId>org.seleniumhq.selenium</groupId>
    <artifactId>selenium-java</artifactId>
    <version>3.141.59</version>
</dependency>