Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

keploy

keploy: A developer-centric API and integration testing tool that auto-generates tests and data mocks from recorded traffic.

What problem it solves

Creating realistic API and integration tests often requires changing application code, adding SDKs, and provisioning external infrastructure. Applications also need a practical way to replay distributed flows involving databases, queues, external APIs, and streaming events.

Key features

  • Code-less traffic capture — Run an application under Keploy to capture real API calls and integration flows as tests and mocks without adding SDKs or modifying application code.

    Source: README

  • Record and replay complex flows — Record and replay distributed API flows as mocks and stubs for use in later test runs.

    Source: README

  • Infrastructure virtualization — Capture dependencies such as databases, queues, streaming services, and external APIs, then replay them deterministically without reprovisioning infrastructure.

    Source: README, internal

  • Coverage and AI-assisted expansion — Calculate statement, branch, API schema, and business use-case coverage, then use recordings and Swagger/OpenAPI schemas to identify missing scenarios and expand coverage.

    Source: README

  • CI/CD workflows and deterministic execution — Run recorded tests with mocks locally, in CI pipelines, or across Kubernetes clusters. Deterministic replay includes support for freezing system time.

    Source: README

Quick start

Copied verbatim from the project's README.

source /dev/stdin <<<"$(curl -fsSL https://keploy.io/install.sh || echo 'echo Keploy installer download failed >&2; return 1')"
keploy record -c "CMD_TO_RUN_APP"
keploy test -c "CMD_TO_RUN_APP" --delay 10

Who it may suit

This may suit developers and QA teams that need API, integration, or E2E tests without changing application code. It may also suit teams working across multiple languages, frameworks, databases, queues, and distributed services.

Topics to discuss

  • Which real-world application flows are most difficult to cover with current testing approaches?

  • How should recorded dependencies be organized and versioned across teams and environments?

  • Which CI/CD and reporting integrations would be most useful for your testing workflow?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/keploy/keploy#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/keploy/keploy

Comments

…