Interesting but would be more useful with support for streaming
On the roadmap, depending on your definition of "streaming" (e.g. buffer streams, websockets).
Polly.js – Record, replay, and stub HTTP interactions
11–20 of 91 posts
Re: Polly.js – Record, replay, and stub HTTP interactions
#12I've used mitmproxy + proxychains to do this. How is Polly different?
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.).
Re: Polly.js – Record, replay, and stub HTTP interactions
#13I would love to hear from people involved in projects like this, what kind of work/ how much, was done to get it ready for and approved to be open sourced by the company. Especially at large corps like Netflix I'm sure there's a lot of hoops to jump through.
Netflix seems to also have a really strong culture around this though, so I wouldn't be surprised if it's a lot less hoopy than you'd imagine.
Re: Polly.js – Record, replay, and stub HTTP interactions
#14How does it hook into the browser APIs? I can't seem to find it.
By what black magic would it know how to hook into my puppeteer instance?
Or I'm I not understand this?
Re: Polly.js – Record, replay, and stub HTTP interactions
#15Also check out https://github.com/code-mancers/interceptor which as well uses browser APIs to enable users to mock http responses via a chrome extension.
Re: Polly.js – Record, replay, and stub HTTP interactions
#16So is this basically selenium in javascript with some neat features?
This isn't selenium. More like wiremock.
Re: Polly.js – Record, replay, and stub HTTP interactions
#17Unrelated but There are so many things called Polly that it gets confusing
Yeah. I was going to bring up the library for .net that provides policy based retries.
Re: Polly.js – Record, replay, and stub HTTP interactions
#18[deleted]
Re: Polly.js – Record, replay, and stub HTTP interactions
#19I know this is slightly different, but I wish more people knew about Chrome / Safari / Firefox’s “network” console tab. Great for debugging. Can look at all requests, headers, responses, timespans, etc. Some will even let you copy a given network request as a cURL command, capturing all headers, body, query strings, etc.
And out of curiosity, what makes you think that people don't know about it? I've never met a web dev who didn't know about it in the past few years.
Re: Polly.js – Record, replay, and stub HTTP interactions
#20Related to that, is there anything that allows to completely save the state of a modern website with all of the fetch requests and websocket related stuff it fired off?
I just want an ability to save and reopen exactly what I'm looking at. There are some cool websites which will eventually go down and I want to preserve an interactive snapshot of them.