LEARNING.md

Learning Outcomes

Step	Title	Concept Covered	Learning objectives	Further Reading
step 1	Create our consumer before the Provider API even exists	Consumer-driven design with Hexagonal Architecture	Understand use case	https://martinfowler.com/articles/consumerDrivenContracts.html
step 2	Write a Pact test for our consumer	Consumer side pact test	Understand basic Consumer-side Pact concepts Understand "Matchers" to avoid test data brittleness Demonstrate that Pact tests are able to catch a class of integration problems	https://docs.pact.io/5-minute-getting-started-guide#scope-of-a-consumer-pact-test https://docs.pact.io/best_practices/consumer
step 3	Create our Provider with Ports & Adapters in mind	Hexagonal Architecture	Understand how to scaffold an provider application, with ports and adapters in mind Highlight our area of interest for our Pact message verifications	TODO LINK
step 4	Verify the consumer pact with the Provider API	Provider side pact test	Understand basic Provider-side Pact concepts Place provider side testing in a broader testing context (e.g. where it fits on the pyramid)	TODO LINK

Further reading

• https://docs.pact.io/getting_started/how_pact_works#non-http-testing-message-pact
• https://dius.com.au/2017/09/22/contract-testing-serverless-and-asynchronous-applications/
• https://dius.com.au/2018/10/01/contract-testing-serverless-and-asynchronous-applications-part-2/
• https://alistair.cockburn.us/hexagonal-architecture/
• https://netflixtechblog.com/ready-for-changes-with-hexagonal-architecture-b315ec967749
• https://docs.aws.amazon.com/prescriptive-guidance/latest/cloud-design-patterns/hexagonal-architecture.html