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
This is a feature request for an new function which mocks an application so that you don't have to start all application dependencies when testing an application. i.e.
This feature is nice, because if you want to mock certain modules in an app, your app might still depend on that app being started, so this is something I'd like to see. It should be fairly easy to implement as well (just respond with a pid, most likely a temp Meck process, for the application callback module).
Activity
horkhe commentedon Oct 23, 2012
It seems like to much to ask from a mocking framework that works on the module level.
eproxus commentedon Oct 23, 2012
This feature is nice, because if you want to mock certain modules in an app, your app might still depend on that app being started, so this is something I'd like to see. It should be fairly easy to implement as well (just respond with a pid, most likely a temp Meck process, for the application callback module).
eproxus commentedon Nov 21, 2016
Closing and documenting in the wiki instead: https://github.com/eproxus/meck/wiki#feature-ideas
Please comment here if you have information or requests to add, and/or want to discuss a PR or possible implementation proposal.