Skip to content

Commit

Permalink
update readme
Browse files Browse the repository at this point in the history
  • Loading branch information
christian-draeger committed Dec 17, 2018
1 parent fa126b3 commit a0dadc7
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -192,7 +192,12 @@ In Terms of Contract Testing you should always proceed according to the followin
* define your contract
* verify your contract against a mock
* publish your contract
* End up implementing
* End up verifying the contract on Producer side

> **_A few words in advance:_ Don't get confused by the Consumer / Producer wording - it is not related to the data flow!**
> **Producer in the context of Pact describes who is providing the API.**
> **That means for instance if you make a POST-request to an API - the API providing application is the _Producer_, where the application that is doing the request is the _Consumer_ on the other hand.**

Regarding the example implementations we will focus on the **[HTTP based integration](#rest-example-server-to-server-communication) first** and _later on_ we having a look at [**messaging queues**](#messaging-example).

Expand All @@ -209,10 +214,6 @@ Defining a Pact should be splitted into 3 steps:

> If you are looking for an example on how to define a contract by using Javascript go [here](#javascript-consumer).
> **_A few words in advance:_ Don't get confused by the Consumer / Producer wording - it is not related to the data flow!**
> **Producer in the context of Pact describes who is providing the API.**
> **That means for instance if you make a POST-request to an API - the API providing application is the _Producer_, where the application that is doing the request is the _Consumer_ on the other hand.**
### Define
We'll start defining our Pact at the **Consumer** Application.
I mean hey, we want to work Consumer Driven and who could know its
Expand Down

0 comments on commit a0dadc7

Please sign in to comment.