Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Added the filter usage in docs #267

Merged
merged 1 commit into from
Nov 30, 2023
Merged

Added the filter usage in docs #267

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion versioned_docs/version-2.0.0/running-keploy/configuration-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ keywords:
- configuration
---

Tired of specifying the same container name, app command, or delay for each record or test command? 😴
Tired of specifying the same container name, app command, or delay, filters for each record or test command? 😴

Introducing Keploy-config 🎉

Expand All @@ -22,3 +22,21 @@ keploy generate-config --path "/path/to/your/project"
```

After successful execution of the command, a default initialized config file has been created. 🥳

## Eliminate recording of test cases

To simplify your test setup, use the filters section in the YAML configuration file. This allows you to exclude requests with specific headers or methods from generating test cases.<br />
For example, to avoid creating test cases for requests with certain headers and for specific URL methods, use the following configuration:

```bash
filters: {
ReqHeader: ["Host","Accept","Accept-Language"],
urlMethods: {
"/home":["GET","POST"],
}
}
```

With this configuration, test cases won't be generated for requests with the specified headers and for GET or POST requests to <strong>"/home"</strong>, simplifying your testing process.


Loading