The Keploy Community is working towards increasing the adoption of integration testing, API testing, mocking, and test generation for cloud-native and microservices-based applications.
One of the ways we track Keploy’s real-world impact is through an ADOPTERS list.
The purpose of this issue is to collect adoption stories via pull requests from organizations and individual developers who are using Keploy in production or development, and to understand how Keploy is being used in real-world workflows.
Who Can Participate
- Organizations using Keploy in their workflows
- Individual developers using Keploy
How to Contribute Your Adoption Story
Please contribute your adoption story by opening a pull request, based on how you use Keploy.
You can use the structure below as guidance.
Contribution Guidelines
1. What are you testing with Keploy?
Briefly describe what you are testing, for example:
- Backend APIs or services
- Microservices within a distributed system
- End-to-end application workflows
- Internal or public APIs
2. Why did you choose Keploy?
- How Keploy helps you (test generation, mocking, regression testing, CI/CD confidence, etc.)
- Any measurable impact (time saved, faster releases, reduced test maintenance, etc.)
3. Where are you using Keploy?
- Local development
- CI/CD pipelines
- Staging or pre-production
- Production
- Open-source or internal projects
Contact / Attribution
If you would like your organization name or individual name to be added to ADOPTERS.md, please include a preferred contact or attribution handle such as:
- GitHub username
- LinkedIn profile
- Twitter/X handle
- Website
Where to Add Your Entry
For Organizations
If your organization is using Keploy, please:
- Create a new file at:
adopters/organizations/<company-name>.md
- Open a pull request and reference this issue
For Individual Users
If you are an individual user, please:
- Create a new file at:
adopters/users/<your-name>.md
- Open a pull request referencing this issue
Your contribution helps strengthen the Keploy ecosystem and provides valuable insights for the community.
The Keploy Community is working towards increasing the adoption of integration testing, API testing, mocking, and test generation for cloud-native and microservices-based applications.
One of the ways we track Keploy’s real-world impact is through an ADOPTERS list.
The purpose of this issue is to collect adoption stories via pull requests from organizations and individual developers who are using Keploy in production or development, and to understand how Keploy is being used in real-world workflows.
Who Can Participate
How to Contribute Your Adoption Story
Please contribute your adoption story by opening a pull request, based on how you use Keploy.
You can use the structure below as guidance.
Contribution Guidelines
1. What are you testing with Keploy?
Briefly describe what you are testing, for example:
2. Why did you choose Keploy?
3. Where are you using Keploy?
Contact / Attribution
If you would like your organization name or individual name to be added to
ADOPTERS.md, please include a preferred contact or attribution handle such as:Where to Add Your Entry
For Organizations
If your organization is using Keploy, please:
adopters/organizations/<company-name>.mdFor Individual Users
If you are an individual user, please:
adopters/users/<your-name>.mdYour contribution helps strengthen the Keploy ecosystem and provides valuable insights for the community.