| Interface | Description |
|---|---|
| Consumer |
Used to pass consumer name to PactRunner
|
| IgnoreNoPactsToVerify |
With this annotation set on the test class, the pact runner will ignore the fact that there are no pacts to verify.
|
| Provider |
Used to pass provider name to PactRunner
|
| State |
Used to mark methods that should be run on state change
|
| TargetRequestFilter |
Annotation to mark a test method as a request filter. The method must receive a single HttpRequest parameter
|
| VerificationReports |
Annotation to control the generation of verification reports
|
| Class | Description |
|---|---|
| FilteredPactRunner |
Pact Runner that uses annotations to filter the interactions that are executed
|
| InteractionRunner |
Internal class to support pact test running Developed with org.junit.runners.BlockJUnit4ClassRunner in mind
|
| MessagePactRunner | |
| PactRunner |
JUnit Runner runs pacts against provider To set up name of tested provider use Provider annotation To point on pact's source use PactBroker, PactFolder or PactSource annotations To point provider for testing use combination of Target interface and TestTarget annotation There is out-of-the-box implementation of Target: HttpTarget that will play interaction from pacts as http request and check http responses Runner supports: - org.junit.BeforeClass, org.junit.AfterClass and org.junit.ClassRule annotations, that will be run once - before/after whole contract test suite - org.junit.Before, org.junit.After and org.junit.Rule annotations, that will be run before/after each test of interaction WARNING: please note, that only org.junit.rules.TestRule is possible to use with this runner, i.e. org.junit.rules.MethodRule IS NOT supported - State - before each interaction that require state change, all methods annotated by State with appropriate state listed will be invoked
|
| RestPactRunner | |
| RunStateChanges |
| Exception | Description |
|---|---|
| MissingStateChangeMethod |