Hi @Aditya90456
Please let me know why are these changes required?
And what is you obervation while recording and replaying it with keploy.

Hi @Aditya90456 Please let me know why are these changes required? And what is you obervation while recording and replaying it with keploy.

Hi @kapishupadhyay22, thanks for the review 🙂

Why these changes are required:
These changes introduce a simple Employee domain model along with a DAO layer to demonstrate end-to-end CRUD operations in a structured way. The goal is to provide a realistic sample use case where Keploy can capture and replay API interactions involving database operations, rather than using inline or ad-hoc logic.

Observations while recording and replaying with Keploy:

During recording, Keploy successfully captured the HTTP requests/responses along with the corresponding database interactions for all CRUD endpoints.

On replay, the test cases were executed deterministically, and the responses matched the recorded behavior without requiring any code changes.

This helped validate that the DAO-based design works well with Keploy’s record/replay flow and makes the sample easier to extend and reason about.

Please let me know if you’d like me to simplify the example further or add more documentation around the Keploy flow. @kapishupadhyay22