Understanding Mocks

Overview

Mocks simulate API behavior without calling the real backend. They help teams validate flows early (or reliably) when real services are:

• unavailable
• unstable/flaky
• still under development

When to use mocks

• frontend development before APIs are ready
• QA validation for multi-step workflows
• negative and edge-case testing that’s hard to reproduce reliably
• CI runs where environment dependency would cause flakes

How mocks typically work

1. Select a project.
2. Define a mock for an endpoint.
3. Choose response style:
   • static (fixed payload)
   • dynamic (templates/variables/conditional behavior)
4. Test the mock response with a sample request.
5. Use mocks during test execution or run them as a standalone mock service (if supported).

Best practices

• Keep mock payloads realistic and schema-aligned.
• Label mocks clearly so production validation doesn’t accidentally rely on them.
• Disable mocks when validating real production behavior.

Related articles

• Understanding workflows
• Endpoint management