|
| 1 | +Say you are the VP of product at Keploy and you want to make this product trending and very well known for its user experience, smooth and clean design and a very developer friendly tool. |
| 2 | + |
| 3 | + |
| 4 | +Keploy has 3 products. |
| 5 | + |
| 6 | +1. Integration Testing Product. That started as open source product to record-replay API calls along with database mocks or any internal/external services mocks. It got popular and got 10K+ stars. Keploy now offers enterprise version of it with features like - timefreezing, deduplication, mock registry, Re-record Mocks, Normalise Report, CI/CD Integration, UI Console, Self hosted data plane, SSO, Audit Logging, Support, recording from k8s environment. Some of these features are in progress for paid enterprise users. |
| 7 | + |
| 8 | +What do we ensure? |
| 9 | +EVERY test generated should.. |
| 10 | + |
| 11 | +✅ Build, Pass - No flaky tests |
| 12 | +⬆️ Coverage - cover new edge case |
| 13 | +✅ Clean tests - no reviews required |
| 14 | +Keploy Test Agent isn't just "another AI writing code". It's a language-trained, vertical AI built JUST for unit testing. |
| 15 | + |
| 16 | +Here's what it actually does: |
| 17 | + |
| 18 | +🔧 Prompt-engineering magic + validations (we run build/run/coverage checks for every test) |
| 19 | + |
| 20 | +🎯 Targets only code changed in the PR — no noisy test spam |
| 21 | + |
| 22 | +🧠 Talks to LLMs like Gemini, GPT, Claude, etc. — picks the best output based on your tech stack |
| 23 | + |
| 24 | +🔒 ISO, GDPR, SOC2, HIPAA compliant |
| 25 | +Setup is as easy as merging a PR (literally): |
| 26 | + |
| 27 | +Install Keploy from GitHub Marketplace |
| 28 | +Enable it on your repo(s) |
| 29 | +Open a PR — Keploy will scan the diff, generate tests, validate them, and push a commit |
| 30 | +Language supported: Golang |
| 31 | + |
| 32 | +Custom LLM models for tailored test generation. |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +3. API Test Generation Product. Keploy recently launched API testing product that takes open API schema/postman collection/curls/url endpoint or any other resources of the application and can create validated test suites with edge cases and flows. It iterates through the api flows with the application multiple times before giving it to the user. It ensures to create the object and then delete it at the end of the flow for db consistency. Also, it allows users to replay these tests to different endpoints at staging/test/QA environemnts with the generated test suites. It also allows users to self-heal tests, label, filter them or share them across teams. Idea is to save QAs time writing edge cases and scripting them. |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | + Let me tell you how it works. |
| 41 | + |
| 42 | +1. Users signup on keploy console and provide their endpoints/schema/curl/postman collection or any other aplication resources so that keploy gets the working curls and can use AI to create api flows for that. Mocks will not be created in this case since it's e2e test, if user wants mocks to, check integration testing product. |
| 43 | + |
| 44 | +2. If a user doesn't have working curls or wants to record the test cases by performing actions on website on chrome and record via keploy browser extension - keploy will convert the interactions to tests with assertions but no mocks. |
| 45 | + |
| 46 | +3. If you have a private URL - install keploy agent locally that will help keploy servers talk to your url and create api calls. |
| 47 | + |
| 48 | + |
| 49 | +how keploy api-testing is different? we create multiple complete api test-sets containing apis flows and make sure that the objects are created first and then perform operation and then do cleaup to so that user doesn't have to setup seed data, etc.. We do that by running the flows multiple times on the same endpoint and seeing if response is different and we then discard it. |
| 50 | + |
| 51 | + |
| 52 | +Users can add more assertions on each test step or can add entire test set by importing curls. |
| 53 | +Users can also use - fix with AI for failing tests so that keploy can fix failing tests. |
| 54 | +Users can also filter/select delete, run tests on any given new testing endpoint and generate/share test reports. |
| 55 | +Users can also integrate running tests in the CI pipeline. |
| 56 | + |
| 57 | +Users can visualise dashboard for their applications. Keploy needs openapi, postman collection, prd and other resources to generate connected flows. It also needs recordings of api tests that can be done using chrome extension for a web application client side or using a local proxy agent if capturing api calls recording locally client side. keploy also self-detects a lot of bugs and does schema validations. |
| 58 | +keploy also finds out self-healing ways of tests cases. It can be connected with AI to expand the api and statement coverage. |
| 59 | + |
| 60 | +it has dashboard and trend charts for all of these. and additional metrics. it can be integrated with unit testing libraries to to view coverage in sonarqube, codecov or any other tool. Kploy also shares test health summary and status ratios. it also finds performance realted issues. all the test cases are version controlled. comes with test data management and auto grouping, parametrization. it executes the test cases and validates them before giving it to developer. it can run in any env, local, staging, qa, dev, cicd, can be triggered anytime concurrently. uses cache and hence lightweight environemnt. does dependency caching |
| 61 | +it has a mock registry and artifacts that can be used independenlty. has soc2, gpr, iso and hippa compliance. supports custom assertions. |
| 62 | + |
| 63 | + |
| 64 | + Product module Feature highlights (one-glance) Consumption unit (module level) |
| 65 | + |
| 66 | +Included quantity |
| 67 | +(monthly) |
| 68 | + |
| 69 | +Integration Testing (self-hosted data plane) |
| 70 | + |
| 71 | +Runtime record/stop |
| 72 | +• Record from any cluster/pod |
| 73 | +• Replay in lower envs/CI |
| 74 | +• Editable YAML tests |
| 75 | +• Selective mocking (true E2E vs isolated) |
| 76 | +• Environment-aware replays |
| 77 | +• Test deduplication & auto-grouping |
| 78 | +• Buggy suite detection (unstable suites flagged) |
| 79 | + |
| 80 | +Test & Mock Generated (shared pool) |
| 81 | + |
| 82 | +40,000 generations / |
| 83 | +month (shared pool) |
| 84 | + |
| 85 | +Service & Infra Virtualization |
| 86 | + |
| 87 | +Auto-capture/mimic dependencies (HTTP/gRPC/DB/Kafka/Redis etc.) |
| 88 | +• Mock registry + artifacts |
| 89 | +• Dependency caching |
| 90 | +• Test data mgmt |
| 91 | +• Parametrization |
| 92 | +• Custom assertions |
| 93 | +• Works offline within your infra for executions |
| 94 | + |
| 95 | +Test & Mock Generated (shared pool) |
| 96 | + |
| 97 | +40,000 generations / |
| 98 | +month (shared pool) |
| 99 | + |
| 100 | +Record–Replay + Intelligent Test Normalization |
| 101 | + |
| 102 | +Intelligent normalization (timestamps/IDs/non-deterministic fields) |
| 103 | +• Noise cancellation rules |
| 104 | +• Stable diffs |
| 105 | +• Multi-run validation to prevent flakes |
| 106 | +• Buggy suite detection + flaky triage |
| 107 | +• Version-controlled artifacts |
| 108 | + |
| 109 | +Test & Mock Generated (shared pool) |
| 110 | + |
| 111 | +40,000 generations / |
| 112 | +month (shared pool) |
| 113 | + |
| 114 | +Coverage Insights (Statement, Schema, Business) |
| 115 | + |
| 116 | +Coverage insights dashboard |
| 117 | +• Schema/Business coverage by API path + fields |
| 118 | +• Statement coverage via unit-test integrations |
| 119 | +• Coverage trends + gap detection |
| 120 | +• “Generate tests for missing coverage” workflows |
| 121 | +• Export to SonarQube/Codecov/etc. |
| 122 | + |
| 123 | +Test & Mock Run (shared pool) |
| 124 | + |
| 125 | +300,000 executions / |
| 126 | +month (shared pool) |
| 127 | + |
| 128 | +CI/CD Integration + CI/CD Runners |
| 129 | + |
| 130 | +Integrations for GitHub/GitLab/Jenkins/Argo/etc. |
| 131 | +• CI/CD runners support (self-hosted runners) |
| 132 | +• PR/pipeline gating • Reports & artifacts |
| 133 | +• Scheduled/on-demand/concurrent runs |
| 134 | +• Cache-based lightweight execution |
| 135 | + |
| 136 | +Test & Mock Run (shared pool) |
| 137 | + |
| 138 | +300,000 executions / |
| 139 | +month (shared pool) |
| 140 | + |
| 141 | +Confidential — This document contains trade secrets and strategic guidance from Keploy. Do not distribute without written |
| 142 | + |
| 143 | +Product module Feature highlights (one-glance) Consumption unit (module level) |
| 144 | + |
| 145 | +Included quantity |
| 146 | +(monthly) |
| 147 | + |
| 148 | +AI-Based E2E Testing + Edge Case Detection |
| 149 | + |
| 150 | +Generate connected flows from recordings + OpenAPI/Postman/PRD |
| 151 | +• Edge case detection + negative scenarios |
| 152 | +• Multi-step E2E chains |
| 153 | +• AI fixes & self-healing suggestions for brittle tests/mocks |
| 154 | +• Auto-validation (run repeatedly, keep stable/new coverage only) |
| 155 | + |
| 156 | +Test Generated |
| 157 | + |
| 158 | +(Counts within |
| 159 | +generation pool) |
| 160 | + |
| 161 | +Contract & Schema Testing |
| 162 | + |
| 163 | +OpenAPI/schema validation |
| 164 | +• Breaking-change detection |
| 165 | +• Contract diffs |
| 166 | +• Custom assertions |
| 167 | +• Schema drift visibility |
| 168 | +• Contract regression in CI |
| 169 | + |
| 170 | +Test Run (shared pool) |
| 171 | + |
| 172 | +(Counts within execution |
| 173 | +pool) |
| 174 | + |
| 175 | +Performance Testing (Available Q1’26) |
| 176 | + |
| 177 | +Replay-based perf baseline |
| 178 | +• Perf regression detection |
| 179 | +• Sampling for high-QPS |
| 180 | +• Trend reporting + anomalies |
| 181 | + |
| 182 | +Test Run (shared pool) |
| 183 | + |
| 184 | +(Counts within execution |
| 185 | +pool) |
| 186 | + |
| 187 | +Analytics & Insights |
| 188 | + |
| 189 | +Trend charts (pass/fail, flaky rate, coverage movement) |
| 190 | +• Test health summary |
| 191 | +• Status ratios |
| 192 | +• Suite quality signals (buggy suite detection) |
| 193 | +• Workspace-level insights across teams |
| 194 | + |
| 195 | +Included Included |
| 196 | + |
| 197 | +Confidential — This document contains trade secrets and strategic guidance from Keploy. Do not distribute without written |
| 198 | + |
| 199 | +Product module Feature highlights (one-glance) Consumption unit (module level) |
| 200 | + |
| 201 | +Included quantity |
| 202 | +(monthly) |
| 203 | + |
| 204 | +Enterprise-grade Security |
| 205 | + |
| 206 | +SOC2/ISO/GDPR/HIPAA aligned controls |
| 207 | +• RBAC/user management |
| 208 | +• Audit-ready workflows |
| 209 | +• Data residency (data plane in your infra) |
| 210 | +• Controlled updates with permission |
| 211 | + |
| 212 | +Included Included |
| 213 | + |
| 214 | +LLM Support |
| 215 | + |
| 216 | +BYO model key |
| 217 | +• Integrate with internal LLM gateway |
| 218 | +• Token/cost analysis • Model policy controls |
| 219 | +• Guardrails for generation quality |
| 220 | + |
| 221 | +Included Included |
| 222 | + |
| 223 | +Implementation & Support |
| 224 | + |
| 225 | +Dedicated onboarding |
| 226 | +• Slack channel |
| 227 | +• Solution engineer support |
| 228 | +• Deployment assistance (4–6 weeks typical) |
| 229 | +• Success criteria + rollout plan |
| 230 | + |
| 231 | +Included Included |
| 232 | + |
| 233 | +Additional Perks |
| 234 | + |
| 235 | +Open-source committer access (as applicable) |
| 236 | +• Priority bug triage |
| 237 | +• Best-practice templates |
| 238 | +• Enablement for QA + Dev teams |
| 239 | + |
| 240 | +Included Included |
0 commit comments