Storage options for mocked data objects #1651
Unanswered
Triendster
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey everyone,
I hope this message finds you all in good health and high spirits. I am reaching out to seek your expertise and insights regarding a specific topic related to using MSW (Mock Service Worker) for mocking responses with prepared data objects.
As a developer who utilizes MSW for API mocking during testing and development, I have encountered the need to store and manage mocked data objects efficiently. While MSW provides a powerful mechanism for intercepting and mocking network requests, I find myself faced with questions about best practices for organizing and storing these mock data objects.
I would greatly appreciate it if you could share your experiences and preferred practices for handling and storing mocked data objects with MSW.
I'd be especially interested in practices where data used for unit tests is stored centrally or locally in a database and queried directly in the request handler and how this form of data storage is handled and accessed within the context of an external Build Agent, e.g. an agent used for task in an Azure DevOps Pipeline.
Beta Was this translation helpful? Give feedback.
All reactions