Download all versions of pact-jvm-server_2.10 JAR files with all dependencies
pact-jvm-server_2.10 from group au.com.dius (version 2.0.8)
pact-jvm-server_2.10 from group au.com.dius (version 2.0.7)
pact-jvm-server_2.10 from group au.com.dius (version 2.0.6)
pact-jvm-server_2.10 from group au.com.dius (version 2.0.5)
pact-jvm-server_2.10 from group au.com.dius (version 2.0.4)
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
If you use sbt, you can run the server with:
$ sbt pact-jvm-server/run
You can build an application bundle with gradle by running (for 2.10 version):
$ ./gradlew :pact-jvm-server_2.10:installApp
This will create an app bundle in `build/2.10/install/pact-jvm-server_2.10`. You can then execute it with:
$ java -jar pact-jvm-server/build/2.10/install/pact-jvm-server_2.10/lib/pact-jvm-server_2.10-2.0.4.jar
or with the generated bundle script file:
$ pact-jvm-server/build/2.10/install/pact-jvm-server_2.10/bin/pact-jvm-server_2.10
By default will run on port `29999` but a port number can be optionally supplied.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter.
For example:
POST http://localhost:29999/create?state=NoUsers '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
Artifact pact-jvm-server_2.10
Group au.com.dius
Version 2.0.4
Last update 18. September 2014
Tags: need 29999 test verify verifier 34423 23443 file bundle only alone platform once random under number interaction create calls endpoint optionally http start recorder then will port query build running version life tests numbers write shutdown aimed install post responsible mock endpoints return implemented supplied nousers ports admin directory implements returned based actions server_2 cause client communicating disk used localhost installapp finalising writes returns cycle execute submitting initialise providing script posting that pact default generated against gradle rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions gradlew application with 43232 check finished generating list provider expected stand target service java server animal_service also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, pact-jvm-consumer_2.10, json4s-native_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, pact-jvm-model_2.10, scala-library,
There are maybe transitive dependencies!
Group au.com.dius
Version 2.0.4
Last update 18. September 2014
Tags: need 29999 test verify verifier 34423 23443 file bundle only alone platform once random under number interaction create calls endpoint optionally http start recorder then will port query build running version life tests numbers write shutdown aimed install post responsible mock endpoints return implemented supplied nousers ports admin directory implements returned based actions server_2 cause client communicating disk used localhost installapp finalising writes returns cycle execute submitting initialise providing script posting that pact default generated against gradle rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions gradlew application with 43232 check finished generating list provider expected stand target service java server animal_service also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, pact-jvm-consumer_2.10, json4s-native_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, pact-jvm-model_2.10, scala-library,
There are maybe transitive dependencies!
pact-jvm-server_2.10 from group au.com.dius (version 2.0.3)
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
$ sbt pact-jvm-server/run
By default will run on port `29999` but a port number can be optionally supplied.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter.
For example:
POST http://localhost:29999/create?state=NoUsers '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
Artifact pact-jvm-server_2.10
Group au.com.dius
Version 2.0.3
Last update 16. August 2014
Tags: need 29999 test verify verifier 34423 23443 file only alone platform once random under number interaction create calls endpoint optionally start http recorder will port query running life tests numbers write shutdown aimed post responsible mock endpoints return implemented nousers supplied ports admin directory implements returned actions based cause client communicating disk used localhost finalising writes returns cycle execute submitting initialise providing posting that default pact generated against rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions with 43232 check list generating finished provider expected stand service target animal_service server also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, pact-jvm-consumer_2.10, slf4j-api, dispatch-core_2.10, pact-jvm-model_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, scala-library,
There are maybe transitive dependencies!
Group au.com.dius
Version 2.0.3
Last update 16. August 2014
Tags: need 29999 test verify verifier 34423 23443 file only alone platform once random under number interaction create calls endpoint optionally start http recorder will port query running life tests numbers write shutdown aimed post responsible mock endpoints return implemented nousers supplied ports admin directory implements returned actions based cause client communicating disk used localhost finalising writes returns cycle execute submitting initialise providing posting that default pact generated against rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions with 43232 check list generating finished provider expected stand service target animal_service server also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, pact-jvm-consumer_2.10, slf4j-api, dispatch-core_2.10, pact-jvm-model_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, scala-library,
There are maybe transitive dependencies!
pact-jvm-server_2.10 from group au.com.dius (version 2.0.2)
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
$ sbt pact-jvm-server/run
By default will run on port `29999` but a port number can be optionally supplied.
## Life cycle
The following actions are expected to occur
* The client calls `/create` to initialise a server with the expected `JSON` interactions and state
* The admin server will start a mock server on a random port and return the port number in the response
* The client will execute its interaction tests against the mock server with the supplied port
* Once finished, the client will call `/complete' on the Admin API, posting the port number
* The pact server will verify the interactions and write the `JSON` `pact` file to disk under `/target`
* The mock server running on the supplied port will be shutdown.
## Endpoints
### /create
The client will need `POST` to `/create` the generated `JSON` interactions, also providing a state as a query parameter.
For example:
POST http://localhost:29999/create?state=NoUsers '{ "provider": { "name": "Animal_Service"}, ... }'
This will create a new running mock service provider on a randomly generated port. The port will be returned in the
`201` response:
{ "port" : 34423 }
### /complete
Once the client has finished running its tests against the mock server on the supplied port (in this example port
`34423`) the client will need to `POST` to `/complete` the port number of the mock server that was used.
For example:
POST http://localhost:29999/complete '{ "port" : 34423 }'
This will cause the Pact server to verify the interactions, shutdown the mock server running on that port and writing
the pact `JSON` file to disk under the `target` directory.
### /
The `/` endpoint is for diagnostics and to check that the pact server is running. It will return all the currently
running mock servers port numbers.
For example:
GET http://localhost:29999/
'{ "ports": [23443,43232] }'
Artifact pact-jvm-server_2.10
Group au.com.dius
Version 2.0.2
Last update 07. August 2014
Tags: need 29999 test verify verifier 34423 23443 file only alone platform once random under number interaction create calls endpoint optionally start http recorder will port query running life tests numbers write shutdown aimed post responsible mock endpoints return implemented nousers supplied ports admin directory implements returned actions based cause client communicating disk used localhost finalising writes returns cycle execute submitting initialise providing posting that default pact generated against rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions with 43232 check list generating finished provider expected stand service target animal_service server also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, pact-jvm-consumer_2.10, json4s-jackson_2.10, scala-library, pact-jvm-model_2.10,
There are maybe transitive dependencies!
Group au.com.dius
Version 2.0.2
Last update 07. August 2014
Tags: need 29999 test verify verifier 34423 23443 file only alone platform once random under number interaction create calls endpoint optionally start http recorder will port query running life tests numbers write shutdown aimed post responsible mock endpoints return implemented nousers supplied ports admin directory implements returned actions based cause client communicating disk used localhost finalising writes returns cycle execute submitting initialise providing posting that default pact generated against rest example diagnostics this call verifying ruby state writing currently randomly response initialising following parameter complete json servers name interactions with 43232 check list generating finished provider expected stand service target animal_service server also occur clients
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, pact-jvm-consumer_2.10, json4s-jackson_2.10, scala-library, pact-jvm-model_2.10,
There are maybe transitive dependencies!
pact-jvm-server_2.10 from group au.com.dius (version 2.0.1)
pact-jvm-server_2.10 from group au.com.dius (version 2.0.0)
pact-jvm-server_2.10
Artifact pact-jvm-server_2.10
Group au.com.dius
Version 2.0.0
Last update 20. July 2014
Tags: server_2 pact
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, pact-jvm-model_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, pact-jvm-consumer_2.10, scala-library,
There are maybe transitive dependencies!
Group au.com.dius
Version 2.0.0
Last update 20. July 2014
Tags: server_2 pact
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies scala-logging-slf4j_2.10, json4s-native_2.10, pact-jvm-model_2.10, slf4j-api, dispatch-core_2.10, unfiltered-netty-server_2.10, json4s-jackson_2.10, pact-jvm-consumer_2.10, scala-library,
There are maybe transitive dependencies!
pact-jvm-server_2.10 from group au.com.dius (version 2.0-RC5)
Page 6 from 8 (items total 71)