Choose the service behavior your test needs.
WireMock lets you define API responses and how they change between requests. Its scenarios support state transitions, inspection, and reset; it is not limited to fixed responses. See WireMock’s stateful behavior documentation.
Molar Clones provides implementations of selected vendor API paths, with test records you can create and inspect. The useful distinction is how much service behavior you want to configure yourself, and whether a Molar clone supports the exact calls your app makes.
Compare setup and supported behavior.
| Decision | WireMock | Molar Clones |
|---|---|---|
| Starting point | Define request mappings, responses, and scenarios. | Choose a supported clone and seed its test data. |
| State changes | Configure transitions between scenario states. | Use the records and transitions implemented by that clone. |
| Coverage to verify | The mappings and scenarios your team maintains. | The documented endpoints, behaviors, and known limits. |
Try a payment that completes late.
Use the same test in your evaluation: create a payment, delay confirmation, and check that account access changes only when your app processes the callback. Inspect both the browser and service state, then reset and run again.
With a configurable mock, your team defines the relevant responses and transitions. With Clones, first check that the payment paths and timing controls you need are supported. Neither approach replaces checking compatibility with the real provider.
Start with the API calls your app makes.
Read the clone catalog and compare its supported paths with your integration. Keep existing WireMock tests where they already cover the behavior you need. Explore Molar Clones for tests that benefit from reusable payment, email, identity, SMS, or storage state.
When to choose which
Choose WireMock when you need full control over HTTP stubs for any service. Choose Molar Clones when you test Stripe, Twilio, email, sign-in or S3 and want state that carries between steps, such as subscriptions, webhooks and clocks, without writing the stubs. Keep WireMock for services outside the clone catalog.