Download pact-jvm-provider_2.11 JAR file with all dependencies
pact-jvm-provider_2.11 from group au.com.dius (version 2.1.13)
Pact provider
=============
sub project of https://github.com/DiUS/pact-jvm
The pact provider is responsible for verifying that an API provider adheres to a number of pacts authored by its clients
This library provides the basic tools required to automate the process, and should be usable on its own in many instances.
Framework and build tool specific bindings will be provided in separate libraries that build on top of this core functionality.
### Running Pacts
Main takes 2 arguments:
The first is the root folder of your pact files
(all .json files in root and subfolders are assumed to be pacts)
The second is the location of your pact config json file.
### Pact config
The pact config is a simple mapping of provider names to endpoint url's
paths will be appended to endpoint url's when interactions are attempted
for an example see: https://github.com/DiUS/pact-jvm/blob/master/pact-jvm-provider/src/test/resources/pact-config.json
### Provider State
Before each interaction is executed, the provider under test will have the opportunity to enter a state.
Generally the state maps to a set of fixture data for mocking out services that the provider is a consumer of (they will have their own pacts)
The pact framework will instruct the test server to enter that state by sending:
POST "${config.stateChangeUrl.url}/setup" { "state" : "${interaction.stateName}" }
Artifact pact-jvm-provider_2.11
Group au.com.dius
Version 2.1.13
Last update 30. March 2015
Tags: libraries they resources appended second test location root tool consumer takes tools authored instruct basic file when config required services under number interaction enter endpoint many project that pact usable names will each example automate this assumed fixture adheres verifying have specific before simple bindings data state mapping build instances running attempted mocking executed paths json generally setup interactions https files functionality subfolders separate post responsible your provides provider framework should master main folder process blob sending arguments opportunity statechangeurl maps library provided statename core server their first pacts github dius clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 17
Dependencies unfiltered-netty-server_2.11, diffutils, scala-library, pact-jvm-matchers_2.11, commons-io, scalatest_2.11, json4s-native_2.11, groovy-all, dispatch-core_2.11, httpclient, jansi, pact-jvm-model_2.11, json4s-jackson_2.11, scala-xml_2.11, http-builder, scala-logging-slf4j_2.11, slf4j-api,
There are maybe transitive dependencies!
Group au.com.dius
Version 2.1.13
Last update 30. March 2015
Tags: libraries they resources appended second test location root tool consumer takes tools authored instruct basic file when config required services under number interaction enter endpoint many project that pact usable names will each example automate this assumed fixture adheres verifying have specific before simple bindings data state mapping build instances running attempted mocking executed paths json generally setup interactions https files functionality subfolders separate post responsible your provides provider framework should master main folder process blob sending arguments opportunity statechangeurl maps library provided statename core server their first pacts github dius clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 17
Dependencies unfiltered-netty-server_2.11, diffutils, scala-library, pact-jvm-matchers_2.11, commons-io, scalatest_2.11, json4s-native_2.11, groovy-all, dispatch-core_2.11, httpclient, jansi, pact-jvm-model_2.11, json4s-jackson_2.11, scala-xml_2.11, http-builder, scala-logging-slf4j_2.11, slf4j-api,
There are maybe transitive dependencies!
Page 1 from 1 (items total 1)