Hey Everyone in this Blog, we will discuss What problem keploy solves, before that, let's discuss : -
What is Keploy 🤔?
Keploy is an open-source no-code E2E Testing Platform that generates test cases and data mocks from real user traffic. Application testing is one of the biggest barriers to achieving truly Continuous Deployments because it's use-case specific. Developers often avoid writing test cases because it's time-consuming.
In a single sentence
Open-source Tool for converting user traffic to Test Cases and Data Stubs
We have heard about a lot of tools that can help us automate our CI/CD Pipelines and make them secure but there is one major blocker still to achieving true continuous delivery which is Testing because it is still very use-case specific and not technology-specific means you can not write a test like a script which will work for every one of your applications and you need to spend efforts and time to write high-quality automation test Suites and sometimes even more than you spend on developing the applications and even after that you can not ensure that there is one metric that will ensure bug-free code and node effects leaking to production. That's the problem in achieving an autonomous testing cycle in the CD process.
What do we all need to Automate this Testing Process?
There are three things, we all need to automate this testing process:
Auto-Generated Test Scripts
Easily Maintained Test Cases
Test Data = Real (Production) Data
That's all we need to automate the testing process.
Let's Discuss different solutions and what are the limitations of those:
- If you want to test in productions you just need to do that shadow testing.
What is shadow testing🤔?
your application is running, serving the user traffic and you put the new version of let's say V2 and try to replicate the same traffic via some services and you try asserting some responses of the previous expected and as well as the new deployment that you are going to make. if those are matching means all the things are working fine.
But the problem is that it works fine with stateless applications. For stateful applications, there are a lot of other dependencies that your application is talking to especially Databases and you can not the same state that you going to test.
How can we deal with that 🤔?
Here Keploy comes into the picture, It generates E2E tests for APIs (KTests) along with mocks or stubs(Kmocks) by recording real-world API calls KTests can be imported as mocks for consumers and vice-versa
also Integrates with the unit test library and tests the results on the CLI
In summary, Keploy is an E2E Testing Platform that automates the creation of test cases and data mocks from real user traffic, addressing the challenges of time-consuming and use-case-specific testing in continuous deployment.
It provides auto-generated test scripts, easily maintainable test cases, and the ability to use real production data for testing. Keploy can handle stateful applications, integrating with unit test libraries and CLI testing, making it a valuable tool for efficient and comprehensive testing in the CI/CD pipeline.
Keploy Hacktoberfest :
And if like the content I write, feel free to follow me on My Twitter