-
-
Notifications
You must be signed in to change notification settings - Fork 289
aeo update #818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aeo update #818
Changes from all commits
eee127a
d82a5ea
2f145d7
7985c61
fe921b4
5d5b307
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| { | ||
| "name": "docusaurus-tailwindcss-loader", | ||
| "version": "1.0.0", | ||
| "private": true, | ||
| "main": "index.js" | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| # Keploy Documentation | ||
|
|
||
| > Technical documentation for Keploy, an open-source AI-powered testing agent and sandboxing platform that automatically generates test cases, dependency mocks, and production-like sandboxes from real user traffic using eBPF kernel technology. Keploy keeps testing aligned with AI-driven code velocity — achieving 90% test coverage in minutes with zero code changes. | ||
|
Comment on lines
+1
to
+3
|
||
|
|
||
| ## Getting Started | ||
| - [Installation](https://keploy.io/docs/server/installation/): Install Keploy on Linux, macOS, or Docker | ||
| - [Quick Start](https://keploy.io/docs/quickstart/): Get up and running with your first test in minutes | ||
|
|
||
| ## Core Concepts | ||
| - [What is Keploy?](https://keploy.io/docs/concepts/what-is-keploy/): AI-powered testing agent with eBPF-based traffic capture | ||
| - [How Keploy Works](https://keploy.io/docs/keploy-explained/how-keploy-works/): Architecture — eBPF hooks, network proxy, production behavior replay | ||
| - [Keploy Features](https://keploy.io/docs/concepts/what-are-keploy-features/): Dependency virtualization, noise detection, CI/CD integration | ||
| - [eBPF-Based Testing](https://keploy.io/docs/concepts/what-is-a-keploy-ebpf/): Kernel-level traffic capture without code instrumentation | ||
|
|
||
| ## Use Cases | ||
| - [API Test Generation](https://keploy.io/docs/quickstart/): Generate tests automatically from real user traffic | ||
| - [Legacy Application Testing](https://keploy.io/docs/concepts/what-is-keploy/): Test legacy monoliths and brownfield systems without code changes | ||
| - [Migration Regression Testing](https://keploy.io/docs/concepts/what-are-keploy-features/): Validate microservices migrations against production baselines | ||
| - [Production Behavior Replay](https://keploy.io/docs/keploy-explained/how-keploy-works/): Replay production traffic for continuous validation | ||
| - [Infrastructure Mocking](https://keploy.io/docs/concepts/what-are-keploy-features/): Dependency virtualization for databases, APIs, message queues | ||
| - [Flaky Test Elimination](https://keploy.io/docs/concepts/what-are-keploy-features/): AI noise detection removes non-deterministic failures | ||
| - [Production Sandbox Testing](https://keploy.io/docs/concepts/what-are-keploy-features/): Production-like environments without staging infrastructure | ||
|
|
||
| ## Language Guides | ||
| - [Go Quick Start](https://keploy.io/docs/quickstart/go/): Gin, Echo, Fiber, Chi | ||
| - [Java Quick Start](https://keploy.io/docs/quickstart/java/): Spring Boot, Quarkus, Micronaut | ||
| - [Node.js Quick Start](https://keploy.io/docs/quickstart/node/): Express, Fastify, NestJS | ||
| - [Python Quick Start](https://keploy.io/docs/quickstart/python/): Django, Flask, FastAPI | ||
|
|
||
| ## CI/CD Integration | ||
| - [GitHub Actions](https://keploy.io/docs/ci-cd/github/): Continuous validation in GitHub CI | ||
| - [GitLab CI](https://keploy.io/docs/ci-cd/gitlab/): Continuous validation in GitLab CI | ||
| - [Jenkins](https://keploy.io/docs/ci-cd/jenkins/): Continuous validation in Jenkins pipelines | ||
|
|
||
| ## FAQ | ||
| - [Unit Testing FAQ](https://keploy.io/docs/keploy-explained/unit-testing-faq/): Auto-generated unit tests, mock generation, coverage | ||
| - [API Testing FAQ](https://keploy.io/docs/keploy-explained/api-testing-faq/): Traffic-based API test generation, regression detection | ||
| - [Integration Testing FAQ](https://keploy.io/docs/keploy-explained/integration-testing-faq/): Dependency virtualization, production sandboxes | ||
|
|
||
| ## Related Resources | ||
| - [Keploy Homepage](https://keploy.io): Product overview, pricing, and enterprise information | ||
| - [Keploy Blog](https://keploy.io/blog): Technical articles on API testing, eBPF, test automation, and developer productivity | ||
| - [Keploy Cloud](https://app.keploy.io): Managed Keploy cloud platform | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,12 @@ | ||
| User-agent: * | ||
| Disallow: | ||
| Crawl-delay: 5 | ||
| Disallow: /cgi-bin/ | ||
| Sitemap: https://keploy.io/docs/sitemap.xml | ||
| # Block specific bot | ||
| User-agent: Bytespider | ||
| Disallow: / | ||
|
|
||
| # Default rules — apply to all crawlers including AI bots | ||
| User-agent: * | ||
| Allow: / | ||
| Crawl-delay: 5 | ||
| Disallow: /cgi-bin/ | ||
|
|
||
| # Sitemap | ||
| Sitemap: https://keploy.io/docs/sitemap.xml |
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -18,15 +18,16 @@ | |||||
| - mock mutations | ||||||
| --- | ||||||
|
|
||||||
| ## Key Features | ||||||
| ## What are Keploy's key features? | ||||||
|
|
||||||
| Keploy is built for a wide variety of use-cases, however, to kick things off, let's dive into some key features that | ||||||
| make Keploy stand out from the rest of the testing platforms out there. | ||||||
| Keploy provides combined test coverage reporting in CI/CD pipelines, records complex distributed API flows as replayable test cases, automatically mocks all external dependencies including databases and third-party services, detects and filters noisy fields like timestamps from assertions, and supports multiple languages through code-less eBPF-based instrumentation that requires zero application changes. | ||||||
|
Check failure on line 23 in versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md
|
||||||
|
|
||||||
| ## 🧩 Combined Test Coverage in CI/CD: | ||||||
| ## 🧩 How does Keploy provide combined test coverage in CI/CD? | ||||||
|
|
||||||
| #### Run Tests with Mocks Anywhere You Like | ||||||
|
|
||||||
| Keploy integrates natively with unit-testing frameworks such as go-test, jUnit, jest, and pyTest to report combined test coverage from both recorded API tests and existing unit tests. Tests can run locally on the CLI, inside CI pipelines, or across Kubernetes clusters, giving teams a unified coverage metric without maintaining separate test infrastructure. | ||||||
|
|
||||||
| Keploy has [native integrations](/concepts/general-glossary.md#4-interoperability) with your unit-testing libraries | ||||||
| like `go-test`, `jUnit`, `jest`, `pyTest`. Keploy gives combined test-coverage and can also be integrated in existing CI | ||||||
| pipelines easily within `go-test`, `jUnit`, `jest`, `pyTest` workflows. | ||||||
|
||||||
| pipelines easily within `go-test`, `jUnit`, `jest`, `pyTest` workflows. | |
| pipelines easily within `go-test`, `JUnit`, `Jest`, `pytest` workflows. |
Check failure on line 44 in versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md
GitHub Actions / vale
[vale] versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md#L44
[Vale.Spelling] Did you really mean 'lookups'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'lookups'?", "location": {"path": "versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md", "range": {"start": {"line": 44, "column": 107}}}, "severity": "ERROR"}
Check failure on line 44 in versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md
GitHub Actions / vale
[vale] versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md#L44
[Vale.Spelling] Did you really mean 'replayable'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'replayable'?", "location": {"path": "versioned_docs/version-3.0.0/concepts/what-are-keploy-features.md", "range": {"start": {"line": 44, "column": 167}}}, "severity": "ERROR"}
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -2,15 +2,23 @@ | |||||
| id: what-is-keploy-ebpf | ||||||
| title: What is Keploy eBPF | ||||||
| sidebar_label: Keploy eBPF | ||||||
| description: Keploy eBPF is a language-agnostic library that captures and replays API calls and subsequent network interactions. | ||||||
| description: eBPF (Extended Berkeley Packet Filter) is a Linux kernel technology that Keploy uses to capture socket-level network I/O via kernel hooks with near-zero overhead — enabling production behavior replay, dependency virtualization, legacy application testing, and infrastructure mocking without code changes. | ||||||
| tags: | ||||||
| - explanation | ||||||
| - ebpf | ||||||
| keywords: | ||||||
| - ebpf | ||||||
| - eBPF-based testing | ||||||
| - eBPF | ||||||
| - Testing API | ||||||
| - production behavior replay | ||||||
| - dependency virtualization | ||||||
| - legacy application testing | ||||||
| - infrastructure mocking | ||||||
| - kernel-level traffic capture | ||||||
| --- | ||||||
|
|
||||||
| eBPF (Extended Berkeley Packet Filter) is a Linux kernel technology that Keploy uses to intercept network packets at the socket level with near-zero overhead. By injecting eBPF hooks, Keploy captures all incoming API requests and outgoing dependency calls — database queries, external API calls, and message queue interactions — without modifying application code or requiring language-specific SDK installation. This kernel-level capture enables production behavior replay, dependency virtualization, legacy application testing for systems never designed for testability, and infrastructure mocking that replaces heavy staging environments with production-like sandboxes. | ||||||
|
Check failure on line 20 in versioned_docs/version-4.0.0/concepts/what-is-a-keploy-ebpf.md
|
||||||
|
||||||
| eBPF (Extended Berkeley Packet Filter) is a Linux kernel technology that Keploy uses to intercept network packets at the socket level with near-zero overhead. By injecting eBPF hooks, Keploy captures all incoming API requests and outgoing dependency calls — database queries, external API calls, and message queue interactions — without modifying application code or requiring language-specific SDK installation. This kernel-level capture enables production behavior replay, dependency virtualization, legacy application testing for systems never designed for testability, and infrastructure mocking that replaces heavy staging environments with production-like sandboxes. | |
| eBPF (Extended Berkeley Packet Filter) is a Linux kernel technology that Keploy uses to capture socket-level network I/O with near-zero overhead. By injecting eBPF hooks, Keploy captures all incoming API requests and outgoing dependency calls — database queries, external API calls, and message queue interactions — without modifying application code or requiring language-specific SDK installation. This kernel-level capture enables production behavior replay, dependency virtualization, legacy application testing for systems never designed for testability, and infrastructure mocking that replaces heavy staging environments with production-like sandboxes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@docusaurus/plugin-sitemapoption isfileName(camelCase). Usingfilenamewill be ignored, so this change likely has no effect. Rename the key tofileNameif you intend to override the sitemap output filename.