You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues to ensure a similar issue has not already been created
Description
Hi, I'm evaluating Mockaco for use in integration tests. I'm hoping to use it to mock the third-party push notification and SMS services as other integrations so that I can confirm that our platform is correctly making the requests to these services.
Previously we were using getsandbox.com but that is now discontinued. I have a number of tests that I need to refactor.
However, I have run into a few limitations which seem to prevent Mockaco from meeting my needs:
The timestamp provided in verification is in format hh:mm, which isn't really specific enough. I would prefer ISO8601 format or at minimum hh:mm:ss. My tests take seconds to run, not minutes, so it's useful to be able to confirm exactly when the request was made.
Sometimes a test might result in multiple requests to the same route with different bodies. Is there any way currently of retrieving the list of calls made to Mockaco?
Proposed solution
Change timestamp property in verification response to ISO8601 format.
Add new special route to clear the cache (e.g. GET /_mockaco/clear or DELETE /_mockaco/verification)
Add new special route to list all calls made to a route (e.g. GET /_mockaco/list?route={route} )
Alternatives
I have considered writing my own mock server to do exactly what I want, but it seems like this functionality would be useful for everyone? I'm open to suggestions for other platforms/software that I could use to achieve my goals.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Can we configure the time format in MockacoOptions, which can be passed through a configuration file or environment variable and take effect globally.
The second and third items should be a relatively simple implementation
Yes, to retain compatibility with existing mockaco consumers it would be better to keep the current timestamp as default with the option to change format to ISO8601
I agree with @wlclass! I've been a little busy in the last weeks to work here, but it would be a good addition to the project, if you guys are interested to implement it. Hopefully I can invest some time coding here soon, but any help before that is appreciated, as the enhacement requests are increasing.
@jkuek you might want to consider the discussion in #105 if you intend to use a container in your integration tests.
Prerequisites
Description
Hi, I'm evaluating Mockaco for use in integration tests. I'm hoping to use it to mock the third-party push notification and SMS services as other integrations so that I can confirm that our platform is correctly making the requests to these services.
Previously we were using getsandbox.com but that is now discontinued. I have a number of tests that I need to refactor.
However, I have run into a few limitations which seem to prevent Mockaco from meeting my needs:
Proposed solution
Alternatives
I have considered writing my own mock server to do exactly what I want, but it seems like this functionality would be useful for everyone? I'm open to suggestions for other platforms/software that I could use to achieve my goals.
Additional context
No response
The text was updated successfully, but these errors were encountered: