Recently, I started working with a new client who have been working on their contract testing implementation for a while and figured out they could use some outside help. I’ve paid them a visit recently, and to make the most out of our time together (there was some travel involved and I could really only spend one day on site with them this time), they sent me a long list of questions that the different development teams have gathered over the past few months.

On Test Automation is a platform dedicated to software testing, test automation, and quality assurance. Readers can find articles, tutorials, and resources on topics such as test automation frameworks, testing strategies, and continuous integration pipelines. Additionally, they can learn about software testing tools, test-driven development (TDD), and agile testing methodologies.

On Test Automation

Contract testing is a complementary technique to functional testing and replaces some integration and end-to-end tests, not tests for individual services. This post explains the fine line between contract testing and testing the implementation of a provider service. It focuses on scenarios in HTTP-based integrations, highlighting what should and should not be included in contract tests to avoid brittle tests and misalignments in expectations between consumers and providers. The discussion emphasizes only asking for necessary properties to maintain flexibility and adaptability.

Contract testing - what (not) to test for - part 1