Blog
Debugging failed Dokkimi tests
How to use dokkimi inspect and dokkimi dump to diagnose assertion failures, missing traffic, database query issues, and service startup failures.
Dokkimi vs. Docker Compose for integration testing
Docker Compose and Dokkimi solve different layers of the integration testing problem. Here is where each one fits and where they overlap.
The bug that returns 200 OK
Your HTTP assertions pass, but your service is silently logging errors. Console log assertions catch what status codes miss.
Variables and data extraction in Dokkimi tests
How to use variables for test data and extract values from responses to chain multi-step workflows.
The $ref pattern: reusable service definitions
How to use $ref to share service, database, and mock definitions across test files and keep your .dokkimi/ folder DRY.
Parallel test execution in Dokkimi
How to run test steps concurrently and execute multiple test definitions in parallel to keep your feedback loop fast.
Testing microservices with real databases
How to seed Postgres, MySQL, MongoDB, or Redis in Dokkimi tests — with fresh, isolated instances instead of shared staging databases.
Mock Stripe, Twilio, and any external API without changing your code
How Dokkimi's network-level mocks let you intercept outbound API calls and return controlled responses — no SDK wrappers or environment variables needed.
Getting started with Dokkimi: your first test in 5 minutes
A step-by-step walkthrough of installing Dokkimi and writing your first integration test.
How Dokkimi's traffic interception works
A technical look at how Dokkimi captures inter-service HTTP traffic using sidecar proxies without modifying your application code.
Why we built Dokkimi
Unit tests mock away the interesting parts. Staging environments drift from reality. We built Dokkimi for integration, E2E, and visual regression testing — without changing your code.