-
Notifications
You must be signed in to change notification settings - Fork 20
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
Integrate Keploy for Testing and Add to CI Pipeline #120
Comments
I'll be working on this ! Can you please assign ? |
@slashexx we need da integration tests, you can probably mock the firebase dependency and see if that works? |
@SkySingh04 I'm trying to use firebase emulators to mock the firebase functionality in the CI and it's kinda unable to access the emulator ports. I'm stuck on that, elephant in the room is the here's a snap of the firebase.json I made PS: I have tried changing the ports and it's all the same error on this. |
Hey @slashexx, let’s dive right in, A Google search, a well-placed cue, So take a breath, don’t lose the fight, |
Hey @SkySingh04 , I hear your call, The ports are wild, the logs unclear, Close this one, let’s call it done, |
Wake up Boys, we are migrating to mongo, so Keploy is on |
We need to integrate [Keploy](https://keploy.io/) into our project for automated end-to-end testing and mock generation. Keploy will help us improve test coverage by capturing API interactions and replaying them during testing. Additionally, it will be integrated into the CI pipeline to ensure consistent and automated testing during the development lifecycle.
Tasks:
Setup Keploy Locally:
Integration with Codebase:
CI Pipeline Integration:
Documentation:
Testing and Verification:
Acceptance Criteria:
Additional Context:
Keploy will capture API interactions during local development and replay them in test environments. This ensures deterministic and reliable tests, reducing the effort needed for manual test case creation.
Please ensure compatibility with our existing CI pipeline tools and ensure no disruptions to other workflows.
The text was updated successfully, but these errors were encountered: