Faults, Record & Replay

Slow down or break proxied traffic on purpose, and record real answers to replay when the service is not there.

BifurcSearch requests, mocks and environments…Ctrl PCommandsCtrl KDevelopment

Acme APIWorkspace

Applications

ServicesHealth bar

Routing

Mappings4Proxy rules3CaptureMail

API

Requests12Mocks5Flows1

Workspace

Environments2Vaults1ConfigAudit log

Settings

main2 unpublished changes on this screenPublish

Forward proxy :8080 runningEngine 0.6.0

How it works

A fault rule adds latency, answers with an error status, drops the connection or resets it, for every request to a host or path, or for a share of them. Add and clear faults from the Faults tab of Proxy rules; the footer shows when any are active. Recording saves the real answers of chosen hosts into a cassette in the workspace, with secrets masked, and replay serves that cassette instead of the real hosts, so a test run does not depend on a third-party API being up.

When to use it

• See how your app behaves when the payments API answers 503 three times in ten.
• Check that a slow dependency triggers your timeout and retry.
• Run tests against recorded answers when the real API is rate-limited or offline.