Your microservices work together. Your tests should too.
TestMesh runs end-to-end integration tests across the full chain — HTTP calls, Kafka events, database state, Redis cache — in a single human-readable YAML flow.
Five test tools for one user action
What your stack does
- 1POST /ordersHTTP
- 2→ Kafka event firedKafka
- 3→ inventory-service updates DBDatabase
- 4→ notification-service sends WebSocketWebSocket
- 5→ cache invalidated in RedisRedis
What your tests cover today
- ✗HTTP testPostman
- ✗Kafka testcustom script
- ✗DB assertionmanual SQL
- ✗WebSocketuntested
- ✗Redisuntested
TestMesh replaces all of them with one flow.
From zero to tested in 3 minutes
Install the CLI, write a flow, run it. That's it.
# Install CLI
go install github.com/test-mesh/testmesh/cli@latest
# Or with Docker
docker compose up -dEvery protocol your stack uses
HTTP & REST
Assert status, headers, and body with expr-lang expressions.
action: http_requestKafka
Produce messages and consume to verify async event flows.
action: kafka_consumerDatabases
Query PostgreSQL directly and assert on rows after API calls.
action: database_querygRPC
Call unary and streaming gRPC services by method name.
action: grpc_callWebSocket
Connect, send messages, and assert received payloads.
action: websocketRedis
Read and assert cache values after service operations.
action: redis_getWhere do you want to start?
I'm new to TestMesh
Start hereInstall the CLI and write your first flow in 5 minutes.
Read more →I want to test my microservices
E2E guideSee a full E2E example testing HTTP, Kafka, and database state.
Read more →I'm migrating from Postman / Cypress
Migration guideMap your existing tests and imports to TestMesh flows.
Read more →Built in the open
“Finally, a tool that tests Kafka and HTTP in one file.”
Developer, microservices team
“Replaced our 200-line bash integration test with 40 lines of YAML.”
Developer, microservices team
“The mock server alone saved us weeks of setup.”
Developer, microservices team
Not just another API tester
Built specifically for integration testing — testing how your services work together.
| Feature | TestMesh | Postman | k6 | Cypress |
|---|---|---|---|---|
| HTTP testing | ✅ | ✅ | ✅ | ✅ |
| Kafka / async | ✅ | ❌ | ❌ | ❌ |
| Database assertions | ✅ | ❌ | ❌ | ❌ |
| gRPC | ✅ | ✅ | ❌ | ❌ |
| WebSocket | ✅ | ✅ | ❌ | ❌ |
| Multi-protocol in one flow | ✅ | ❌ | ❌ | ❌ |
| YAML-defined flows | ✅ | ❌ | ❌ | ❌ |
| Runs locally, no signup | ✅ | ❌ | ✅ | ✅ |
| Mock server built-in | ✅ | ✅ | ❌ | ❌ |
Postman is great for API development. k6 is great for load testing. TestMesh is built for integration testing — testing how your services work together.
Stop testing protocols in isolation.
Write one flow that tests the whole chain.