Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Usage Example" isn't an example. #1

Open
ph-ms opened this issue Feb 6, 2017 · 2 comments
Open

"Usage Example" isn't an example. #1

ph-ms opened this issue Feb 6, 2017 · 2 comments

Comments

@ph-ms
Copy link

ph-ms commented Feb 6, 2017

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.

@gubber
Copy link
Collaborator

gubber commented Feb 8, 2017

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.

@ph-ms
Copy link
Author

ph-ms commented Feb 8, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants