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
Refer http://todobackend.com/ for an easy to fork technology that would allow you to pass 'specs' 9in page, JavaScript) in a build for a virtualizaed backend.
The example should perhaps showcase recording/capturing, and how that recorded data could be used programmatically to mock out the backend for the sake of passing the JS specs. Note: recording/capture can't just keep a map of responses, as there's statefulness in the interactions, thus weld having an (re)programmable mode is key.
The text was updated successfully, but these errors were encountered:
Thanks for your comment, some interesting ideas in there, as you might be able to tell I didn't ever develop weld beyond it's initial proof of concept. But maybe it's worth revisiting and turning in to something useful.
OK - well opensource can be a huge commitment. Others in the field include Mountebank, Hoverfly, Bokor, WireMock, machzqcq/service_virtualization, epam/Wilma, and BaiduQA/terminator
Refer http://todobackend.com/ for an easy to fork technology that would allow you to pass 'specs' 9in page, JavaScript) in a build for a virtualizaed backend.
The example should perhaps showcase recording/capturing, and how that recorded data could be used programmatically to mock out the backend for the sake of passing the JS specs. Note: recording/capture can't just keep a map of responses, as there's statefulness in the interactions, thus weld having an (re)programmable mode is key.
The text was updated successfully, but these errors were encountered: