Mockito utility classes for easy integration with TestNG

dependencies {
  testCompile "org.mockito:mockito-testng:VERSION"
}

<dependency>
  <groupId>org.mockito</groupId>
  <artifactId>mockito-testng</artifactId>
  <version>VERSION</version>
  <scope>test</scope>
</dependency>

For latest version, see the releases.

Simply add @Listeners annotation on your test class

import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.testng.MockitoTestNGListener;
import org.testng.annotations.Listeners;
import org.testng.annotations.Test;
import java.util.Map;
@Listeners(MockitoTestNGListener.class)
public class MyTest {
    @Mock
    Map map;
    @InjectMocks
    SomeType someType;
    @Test
    void test() {
        // ...
    }
}

MockitoTestNGListener will do job for you and initialize all fields annotated with mockito annotations.

By default MockitoSession is started with STRICT_STUBS.
You can change this behavior by adding @MockitoSettings to your test class.

import org.mockito.quality.Strictness;
import org.mockito.testng.MockitoTestNGListener;
import org.mockito.testng.MockitoSettings;
import org.testng.annotations.Listeners;
@Listeners(MockitoTestNGListener.class)
@MockitoSettings(strictness = Strictness.WARN)
public class MyTest {
 // ...
}

• MockitoSession is started before each test method or before method annotated with @BeforeMethod, another annotations @BeforeXXX aren't supported #40

• open in IDEA to develop or run ./gradlew idea and then open in IDEA
• ./gradlew build - tests code and assembles artifacts
• ./gradlew publishToMavenLocal - publishes to local Maven repo, useful for local testing

Every merged pull request is published to Maven Central. Actually, any change on master that happily builds on CI is published. The release automation uses Shipkit framework (https://shipkit.org).

The original TestNGListener was a part of the core Mockito repository. However, the jar was never released. Core Mockito team does not work with TestNG so it was hard for us to maintain TestNG integration. In Summer 2018 we moved the TestNG integration to a separate repository under "Mockito" organization.

We are looking for maintainers of TestNG integration! Let us know if you want to join. Mockito core team has limited capacity and focuses on the core library.