4 ms·
I've used mitmproxy + proxychains to do this. How is Polly different?
by Osiris 8y ago
I've used mitmproxy + proxychains to do this. How is Polly different?
- jonknee 8y agohttps://netflix.github.io/pollyjs/#/README https://netflix.github.io/pollyjs/#/README Why Polly? Keeping fixtures and factories in parity with your APIs can be a time consuming process. Polly alleviates this by recording and maintaining actual server responses without foregoing flexibility. * Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests. * Use Polly's client-side server to modify or intercept requests and responses to simulate different application states (e.g. loading, error, etc.).
- curun1r 8y agoNot sure that tells me how it's different from replay or the other half dozen npm modules that do the same thing. It'd be nice for them to contrast their tool with existing ecosystem options considering some of them are pretty well established.
- jasonmit 8y agoCan you share which libraries you know that achieve the same thing? I'm happy to go through and respond to the differences.
- curun1r 8y agoI only have experience with replay, but an npm search turns up: replay, replayer, http-record, talkback, sepia, mitm-record, fetch-vcr, tape-nock, jest-playback, eight-track, axios-vcr, replayer, node-vcr, mocha-vcr, mockyeah, yakbak, nine-track, dkastner-replay, node-nock At which point I stopped looking...recording http requests isn't exactly new territory.
- simplify 8y agoI've personally used node-replay with great success. It has minimal configuration https://github.com/assaf/node-replay https://github.com/assaf/node-replay