Group : au.com.dius

pact-jvm-consumer-groovy_2.11

au.com.dius » pact-jvm-consumer-groovy_2.11

pact-jvm-consumer-groovy ========================= Groovy DSL for Pact JVM ##Dependency The library is available on maven central using: * group-id = `au.com.dius` * artifact-id = `pact-jvm-consumer-groovy_2.11` * version-id = `2.4.x` or `3.3.x` ##Usage Add the `pact-jvm-consumer-groovy` library to your test class path. This provides a `PactBuilder` class for you to use to define your pacts. For a full example, have a look at the example JUnit `ExampleGroovyConsumerPactTest`. If you are using gradle for your build, add it to your `build.gradle`: dependencies { testCompile 'au.com.dius:pact-jvm-consumer-groovy_2.11:3.3.8' } Then create an instance of the `PactBuilder` in your test. ```groovy @Test void "A service consumer side of a pact goes a little someth

更新时间: 2018-09-09 12:48

pact-jvm-server_2.11

au.com.dius » pact-jvm-server_2.11

Pact server =========== The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based. The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON` interactions, running the tests and communicating with the server. The server implements a `JSON` `REST` Admin API with the following endpoints. / -> For diagnostics, currently returns a list of ports of the running mock servers. /create -> For initialising a test server and submitting the JSON interactions. It returns a port /complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk. ## Running the server ### Versions 2.2.6+ Pact server takes the

更新时间: 2018-05-06 19:11

pact-specification-test_2.10

au.com.dius » pact-specification-test_2.10

Pact Specification ================== The [Pact Specification](https://github.com/bethesque/pact_specification) is a robust set of tests on the pact matching code aimed at ensuring pact library implementations across different languages have the same matching behaviour. Without adhering to these specifications there would be room for subtle issues to arise between consumers and providers using different libraries. We are currently aiming for 1.0.0 of the specification, however it is still in development.

更新时间: 2018-04-14 20:31

pact-jvm-server_2.10

au.com.dius » pact-jvm-server_2.10

Pact server =========== The pact server is a stand-alone interactions recorder and verifier, aimed at clients that are non-JVM or non-Ruby based. The pact client for that platform will need to be implemented, but it only be responsible for generating the `JSON` interactions, running the tests and communicating with the server. The server implements a `JSON` `REST` Admin API with the following endpoints. / -> For diagnostics, currently returns a list of ports of the running mock servers. /create -> For initialising a test server and submitting the JSON interactions. It returns a port /complete -> For finalising and verifying the interactions with the server. It writes the `JSON` pact file to disk. ## Running the server ### Versions 2.2.6+ Pact server takes the

更新时间: 2018-04-14 20:13

pact-jvm-provider_2.10

au.com.dius » pact-jvm-provider_2.10

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

更新时间: 2018-04-14 20:06

pact-jvm-provider-specs2_2.10

au.com.dius » pact-jvm-provider-specs2_2.10

pact-jvm-provider-specs2 ======================== Provides an extension to Specs2 Specification to validate a pact file against a running provider. See [ExampleProviderSpec.scala](pact-jvm-provider-specs2/src/test/scala/au/com/dius/pact/provider/specs2/ExampleProviderSpec.scala) for an example. *Note:* The Pact ProviderSpec requires spec2 3.x

更新时间: 2018-04-14 20:04

pact-jvm-provider-scalatest_2.10

au.com.dius » pact-jvm-provider-scalatest_2.10

pact-jvm-provider-scalatest ======================== Provides an extension to scalatest to validate pact files against a running provider. See [examples](src/test/scala/au/com/dius/pact/provider/scalatest) for details. *Note:* The Pact ProviderSpec requires scalatest 2.2.x

更新时间: 2018-04-14 20:03

pact-jvm-provider-maven_2.10

au.com.dius » pact-jvm-provider-maven_2.10

Maven plugin to verify a provider [version 2.1.9+] ================================================== Maven plugin for verifying pacts against a provider. The Maven plugin provides a `verify` goal which will verify all configured pacts against your provider. ## To Use It ### 1. Add the pact-jvm-provider-maven plugin to your `build` section of your pom file. ```xml <build> [...] <plugins> [...] <plugin> <groupId>au.com.dius</groupId> <artifactId>pact-jvm-provider-maven_2.11</artifactId> <version>2.1.9</version> </plugin> [...] </plugins> [...] </build> ``` ### 2. Define the pacts between your consumers and providers You define all the providers and consumers within the configuration element of the maven plugin. ```xml

更新时间: 2018-04-14 20:01

pact-jvm-provider-lein_2.10

au.com.dius » pact-jvm-provider-lein_2.10

# Leiningen plugin to verify a provider [version 2.2.14+, 3.0.3+] Leiningen plugin for verifying pacts against a provider. The plugin provides a `pact-verify` task which will verify all configured pacts against your provider. ## To Use It ### 1. Add the plugin to your project plugins, preferably in it's own profile. ```clojure :profiles { :pact { :plugins [[au.com.dius/pact-jvm-provider-lein_2.11 "3.0.3" :exclusions [commons-logging]]] :dependencies [[ch.qos.logback/logback-core "1.1.3"] [ch.qos.logback/logback-classic "1.1.3"] [org.apache.httpcomponents/httpclient "4.4.1"]] }}} ``` ### 2. Define the pacts between your consumers and providers

更新时间: 2018-04-14 20:00

pact-jvm-provider-junit_2.10

au.com.dius » pact-jvm-provider-junit_2.10

# Pact junit runner ## Overview Library provides ability to play contract tests against provider service in JUnit fashionable way. Supports: - Out-of-the-box convenient ways to load pacts - Easy way to change assertion strategy - **org.junit.BeforeClass**, **org.junit.AfterClass** and **org.junit.ClassRule** JUnit annotations, that will be run once - before/after whole contract test suite - **org.junit.Before**, **org.junit.After** and **org.junit.Rule** JUnit annotations, that will be run before/after each test of interaction - **au.com.dius.pact.provider.junit.State** custom annotation - before each interaction that require state change, all methods annotated by State with appropriate state listed will be invoked ## Example of test ```java @RunWith(PactRunner.class) // Say J

更新时间: 2018-04-14 19:58

pact-jvm-provider-gradle_2.10

au.com.dius » pact-jvm-provider-gradle_2.10

pact-jvm-provider-gradle ======================== Gradle plugin for verifying pacts against a provider. The Gradle plugin creates a task `pactVerify` to your build which will verify all configured pacts against your provider. ## To Use It ### For Gradle versions prior to 2.1 #### 1.1. Add the pact-jvm-provider-gradle jar file to your build script class path: ```groovy buildscript { repositories { mavenCentral() } dependencies { classpath 'au.com.dius:pact-jvm-provider-gradle_2.10:2.2.1' } } ``` #### 1.2. Apply the pact plugin ```groovy apply plugin: 'au.com.dius.pact' ``` ### For Gradle versions 2.1+ ```groovy plugins { id "au.com.dius.pact" version "2.2.1" } ``` ### 2. Define the pacts between your consumers and providers ```groovy pact {

更新时间: 2018-04-14 19:56

pact-jvm-matchers_2.10

au.com.dius » pact-jvm-matchers_2.10

Pact JVM Matchers ================= Implements matchers for pact requests and responses.

更新时间: 2018-04-14 19:54

pact-jvm-logging_2.11

au.com.dius » pact-jvm-logging_2.11

pact-jvm-loggin --------------- Inlined logging from https://github.com/typesafehub/scalalogging to support both Scala 2.10 and 2.11

更新时间: 2018-04-14 19:53

pact-jvm-logging_2.10

au.com.dius » pact-jvm-logging_2.10

pact-jvm-loggin --------------- Inlined logging from https://github.com/typesafehub/scalalogging to support both Scala 2.10 and 2.11

更新时间: 2018-04-14 19:52

pact-jvm-consumer_2.10

au.com.dius » pact-jvm-consumer_2.10

Pact consumer ============= Pact Consumer is used by projects that are consumers of an API. Most projects will want to use pact-consumer via one of the test framework specific projects. If your favourite framework is not implemented, this module should give you all the hooks you need. Provides a DSL for use with Java to build consumer pacts. ## Dependency The library is available on maven central using: * group-id = `au.com.dius` * artifact-id = `pact-jvm-consumer_2.11` * version-id = `2.2.x` ## DSL Usage Example in a JUnit test: ```java import au.com.dius.pact.model.MockProviderConfig; import au.com.dius.pact.model.PactFragment; import org.junit.Test; import java.io.IOException; import java.util.HashMap; import java.util.Map; import static org.junit.Assert.assertEquals; public

更新时间: 2018-04-14 19:51
共7页 , 总 94
索引仓库
仓库 个数
Central 592045