Contract Driven Development

Micro-services done right without the pain of integration
Play Video
Supported Specification Standards

Shift left and kill integration tests

by leveraging API specifications as executable contracts to
identify compatibility issues between your microservices early in your development cycle

API Specifications as Executable Contracts

NO CODE

Contract as Test

Turn your API Specification into tests for free (No Code) and run them against your Services to identify integration issue early
SMART MOCKS

Contract as Stub

No more stale stubs. Specmatic’s “Smart Service Virtualization” verifies your expecations / stub responses against your API Specifications
API SPEC VS SPEC

Backward Compatibility

Identify backward incompatible changes just by comparing two versions of your API Specifications with our unique “No Code” approach.

API Specifications as Executable Contracts

Specmatic supercharges your API Specifications by leveraging them as “Executable Contracts”. Specmatic does this by

Smart Service Virtualization

Allows Consumer Application Development and Testing to progress independent of the Provider Application

API Specifications as Contract Tests

Generates Tests based on the API Specification File without you having to write any code

Contract as Test

Tests for Free – Specmatic parses your API Specification files and based on this generates requests which are fired at your application. It then verifies if your application’s response is as per your API Specification. All this with a “No Code” approach.

Positive Tests

Verify if the API implementation meets basic criteria as per your API Specification

Negative Tests

Verify boundary conditions to identify error handling, unexpected behavior, etc.

Contract as Stub

A component test setup should be able to isolate the “System Under Test” from its dependencies. Smart Service Virtualization enables you to achieve this by truly emulating the dependencies.

Smart Service Virtualization

Validates Expectations against API Specifications to make sure that that stub is truly representative of the Provider

Static and Dynamic Stubbing

Expectations can be set either at startup or dynamically at runtime (for workflow testing) through a http endpoint to Specmatic.

Backward Compatibility

As API Specifcation authors / API designers it is important for us understand if our changes to existing APIs can break compatibility with existing API Consumers / Clients.

Specmatic can perform “Contract vs Contract” testing between two versions of your API Specification file and provide accurate results about backward compatibility breaking changes. Since this is a completely “No Code” capability, you do not have to write any code on the API Client or Service Applications.

Treat Contract as Code

Specmatic and Contract Driven Development promotes treating your API Specifications as code and storing them in a Version Control System where they truly belong.

Central Contract Repo

The “Single Source of Truth” for all your API Specifications so that stakeholders across the organization are on the same page.

Pull/Merge Request based Collaboration

Specmatic can help you identify backward compatibility breaking changes automatically as part of your pre-merge checks so that you can focus on API Design

Unleash the power of API Specifications

No Code

All capabilities of Specmatic are designed with a No Code approach in mind

Multiple Protocols

Http, Kafka, SOAP and more

Platform Independent

Use the command line to integrate with any programmatic environment

Language Agnostic

Specmatic is Programming Language agnostic since it is working at the API level

Proxy Mode

As part of Smart Service Virtualization select endpoints and let other request pass through to real Provider / service

Capture API Specifications

In Proxy Mode, Specmatic can capture your traffic and convert it into API Specifications

Negative Testing

Verify boundary conditions in your API implementations without writing a single line of code

Woven into your CI Pipelines

Trigger Provider and Consumer CI builds when any of the contracts change

Import your APIs

Use Postman Collections or Specmatic’s http proxy to create API Specifications