diff --git a/docusaurus.config.js b/docusaurus.config.js
index 20f3468d3..5a66c4a43 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -1,8 +1,8 @@
//@ts-check
-import { themes as prismThemes } from "prism-react-renderer";
+import {themes as prismThemes} from "prism-react-renderer";
const path = require("path");
-import { visit } from "unist-util-visit";
+import {visit} from "unist-util-visit";
const FontPreloadPlugin = require("webpack-font-preload-plugin");
/** @type {import('@docusaurus/types').DocusaurusConfig} */
@@ -51,7 +51,7 @@ module.exports = {
content:
"API testing, Keploy docs, incident replay, network calls, code paths, test scenarios, code coverage, stubs, junit, go-test, live environment, production incidents, open source, regression tests, ai tests",
},
- { name: "twitter:card", content: "summary_large_image" },
+ {name: "twitter:card", content: "summary_large_image"},
],
headTags: [
// Preconnect tag
diff --git a/versioned_docs/version-3.0.0/running-keploy/cli-commands.md b/versioned_docs/version-3.0.0/running-keploy/cli-commands.md
index 49c6bed1b..6cfdcb3e5 100755
--- a/versioned_docs/version-3.0.0/running-keploy/cli-commands.md
+++ b/versioned_docs/version-3.0.0/running-keploy/cli-commands.md
@@ -31,7 +31,6 @@ Here are some examples of how to use some common flags:
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `record` | `-c, --command`, `--config-path`, `--containerName`, `-d, --delay`, `--metadata`, `-n, --networkName`, `--passThroughPorts`, `-p, --path`, `--proxyport`, `--debug` |
| `test` | `--apiTimeout`, `-c, --command`, `--config-path`, `--containerName`, `-d, --delay`, `--mongoPassword`, `-n, --net, --networkName`, `--passThroughPorts`, `-p, --path`, `--proxyport`, `-t, --testsets`, `--debug`, `-g, --generateTestReport`, `--removeUnusedMocks`, `--coverage`, `--goCoverage`, `--ignoreOrdering`, `--skip-preview`, `--proto-dir`, `--proto-file`, `--proto-include` |
-| `gen` | `--sourceFilePath`, `--testFilePath`,`--coverageReportPath`,`--testCommand`,`--coverageFormat`,`--expectedCoverage`,`--maxIterations`,`--testDir`,`--llmBaseUrl`,`--model`,`--llmApiVersion` |
| `normalize` | `-p, --path`, `--test-run`, `--tests` |
| `rerecord` | `--test-sets`, `-t` |
| `report` | `--test-sets, -t`, `-p, --path`, `--report-path, -r`, `--body` |
@@ -257,40 +256,6 @@ keploy test [flags]
> **Note for GRPC Tests:** When running GRPC test cases, it's recommended to provide proto information using either `--proto-file` or `--proto-dir` flags. If proto information is not provided, Keploy will use basic canonical matching of the protoscopic textual format of GRPC response body, which may be less accurate than proto-based comparison.
-## [gen](#gen)
-
-The `gen` cmd in Keploy allows user to generate unit tests using LLM Models.
-
- Usage:
-
-```bash
-keploy gen [flags]
-```
-
- Available flags:
-
-- `sourceFilePath` - Path to the source file for which tests are to be generated.
-
-- `testFilePath` - Path where the generated tests will be saved.
-
-- `coverageReportPath` - Path to generate the coverage report.
-
-- `testCommand` - Command to execute tests and generate the coverage report.
-
-- `coverageFormat` - Type of the coverage report by default report is in "cobertura" format.
-
-- `expectedCoverage` - Desired coverage percentage by default it is set to be at 100%.
-
-- `maxIterations` - Maximum number of iterations for refining tests (default 5).
-
-- `testDir` - Directory where tests will be written.
-
-- `llmBaseUrl` - Base url of the llm.
-
-- `model` - Specifies the AI model to use by default it uses "gpt-4o" model.
-
-- `llmApiVersion` - API version of the llm if any.
-
## [normalize](#normalize)
The `normalize` cmd in Keploy allows user to change the response of the testcases according to the latest test run response that is executed by the user, this is useful when the API response of the testcases are changed due to code change or any other intentional change in the application.