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.

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

[bug]: Keploy is exhibiting unexpected behavior when used with applications that have two or more databases #1209

Closed
1 task done
charankamarapu opened this issue Dec 15, 2023 · 0 comments · Fixed by #1214
Assignees
Labels
bug Something isn't working keploy

Comments

@charankamarapu
Copy link
Member

charankamarapu commented Dec 15, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

  1. In record mode, When Generic dependency(Redis) is used in the application the expected behaviour is that the application run without any problem, but the dependency is getting timed out and giving error.

  2. In test mode, when Generic dependency(Redis) is used in the application and few mock requests like ping calls and quit calls which are not recorded in record mode are encountered, the expected behaviour should be that parser calls the real database via passthrough. But as approximate matching is implemented the calls are getting matched to some other request and incorrect response is supplied in the parser.

  3. In test mode when I run the the application, The application behaves unexpected because there are 2 mocks with same request but different response lets say MockRequest-1 ~ MockResponse-1 and MockRequest-1 ~ MockResponse-2, according to the application when it sends MockRequest-1 for first time it should receive MockResponse-1 and for second time it should receive MockResponse-2. But the situation is vice versa in actual which is causing the error.

  4. In test mode when I run the application in one of the dependency, a mock gets matched but when comes to reset the mock list some other mock gets deleted. There can be few race conditions with resetting the mock list.

Steps to reproduce

  1. Try an application with two dependencies Mongo and Redis with Keploy and record and test few calls. The issue will be replciated.

Environment

Release

Version

Cloud

Repository

keploy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working keploy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant