Forum Discussion
omatzura
18 years agoSuper Contributor
Hi Philippe!
Definitely, we just didn't manage to squeeze it into the schedule for this release, which was already way late.. Mocking HTTP Responses currently can be done either with an onRequest script as you have done, or by using the docroot setting in the MockService options dialog for mocking static content. Ultimately there will be another tab in the MockService editor named "Resources" containing a list of MockResources which in turn dispatch to MockHttpResponses.. (or something..), and an accompanying HttpMockResponse TestStep. Any further ideas/suggestions are of course always welcome!
regards,
/Ole
eviware.com
Definitely, we just didn't manage to squeeze it into the schedule for this release, which was already way late.. Mocking HTTP Responses currently can be done either with an onRequest script as you have done, or by using the docroot setting in the MockService options dialog for mocking static content. Ultimately there will be another tab in the MockService editor named "Resources" containing a list of MockResources which in turn dispatch to MockHttpResponses.. (or something..), and an accompanying HttpMockResponse TestStep. Any further ideas/suggestions are of course always welcome!
regards,
/Ole
eviware.com