This open-source tool is changing how API tests are written.
→ Keploy
Most tests today are built on assumptions:
• mocked APIs
• clean inputs
• controlled flows
But production doesn’t behave like that.
So you get:
tests passing
bugs in production
Keploy takes a different approach.
It doesn’t simulate your system.
It captures it.
Using eBPF, it records real traffic
→ and turns it into test cases automatically
That means it captures:
• actual API calls
• real DB queries
• async flows
• external services
Then replays everything deterministically.
No SDKs
No code changes
No fragile mocks
Here’s the shift:
If something breaks once in production
→ it becomes a test case forever
You’re not writing tests anymore
you’re capturing what actually happens
Here's the Github : github.com/keploy/keploy
Tdd Vs Bdd: Differences, Benefits, And Use Cases (Updated) #how-to-implement-tdd-in-project" target="_blank" rel="nofollow noopener">keploy.io/blog/community…
Keploy is an open source testing tool that records API calls database queries and streaming events and replays them as test cases and mocks. It uses eBPF to capture traffic at the network layer enabling code less and language agnostic testing with faster execution than traditional unit tests and seamless CI CD integration.
nosubscription.org/software/keplo…
🚨 BREAKING: Someone just open sourced a testing tool that generates API tests and mocks automatically -- by recording real traffic at the network layer using eBPF.
It's called Keploy. And it's not a code generator.
It's a language-agnostic testing agent that captures every API call, database query, and streaming event your app makes in production -- then replays them as tests with zero code changes required.
Here's what makes it different from every other testing tool:
→ Uses eBPF to intercept traffic at the kernel level -- no SDK, no instrumentation, no code changes
→ Records Postgres, MySQL, MongoDB, Kafka, RabbitMQ, Redis -- not just HTTP endpoints
→ Replays tests deterministically without re-provisioning any infrastructure
→ Freezes system time during replay so time-dependent tests don't flake
→ Works with Go, Java, Python, Node.js, Rust, C#, Ruby, Elixir, PHP, Kotlin, Swift -- any language
→ Generates combined coverage: statement coverage for devs, API schema coverage for QA
→ Uses AI to expand coverage from existing recordings -- finds boundary values, wrong types, missing fields
Here's the wildest part:
Most API testing tools only mock HTTP endpoints.
Keploy records the entire infra layer -- your database queries, your message queue events, your external API calls -- and virtualizes all of it so tests run in complete isolation.
No containers to spin up. No test databases to provision. No flaky environment issues.
One command to start recording:
`keploy record -c "CMD_TO_RUN_APP"`
Listed on the CNCF Landscape. 472 releases. Actively maintained.
16.2K GitHub stars. 2.2K forks.
100% Open Source. Apache-2.0 License.
github.com/keploy/keploy
I am currently building SQLite as a service, and this is the best article about database pg wire protocols anyone interested in #databases should read: linkedin.com/pulse/what-pos…
Have you tried @Keploy yet?
If not, you’re missing out a lot! 🚀
In this video, I’ll show you how easy it is to use Keploy to auto-generate test cases for your app – no manual test writing needed.
Go ahead, try it in your project and see the magic yourself! ✨
#keploy
That adorable orange creature is our spirit animal fr 🥹
Because we are beyond ecstatic that we get to say that Keploy is our In Kind Sponsor for HackSpire'25. The FIEM ACM Students' Chapter really couldn't have asked for more 😭
#HackSpire2025#InnovateToInspire
Building Chapi (chat-first API tests ⚡) but worried about strong players like Keploy, Octomind, Postman.
How do you find your wedge + first users in a crowded devtools market? 🤔 #buildinpublic
@Keployio Great to see Keploy focusing on Python automation testing! This is super relevant for anyone looking to optimize their development workflow. Definitely checking out that guide. 🚀 #Python#AutomationTesting