Weird that they'd pick a red panda for the logo.
Prototype: Puppeteer for Firefox
111–120 of 133 posts
Re: Prototype: Puppeteer for Firefox
#112Anyone who wants to play around with some Puppeteer examples, I built https://puppeteersandbox.com . If you want to record your own scripts, I also am actively developing https://checklyhq.com/Puppeteer-recorder , a Chrome extension.
That second link is a 404, although I love your 404 page GIF =)
Checkly looks like a great product!
Re: Prototype: Puppeteer for Firefox
#113Earlier quoted context omitted.
Much better access to low-level information. You can hook (and mock) requests, see what POST data was sent and basically do lots of magic. Also, my experience with Selenium under Python is that doing anything bigger quickly turns into one giant timing hack.
If it really E2E from user perspective you shouldn't doing any magic and manipulate POST data.
[deleted]
Re: Prototype: Puppeteer for Firefox
#114Earlier quoted context omitted.
You're not technically wrong, but unit/integration/E2E are not hard categories for tests, they're just points along a continuum. Sometimes I want to directly control a browser to run a test or examine a UI component, but I still want to mock parts of my application. This is one of the biggest weaknesses with Selenium -- it takes a very narrow view of what testing is, so it becomes much less useful as soon as you're t…
>This is one of the biggest weaknesses with Selenium -- it takes a very narrow view of what testing is Selenium/WebDriver isn't a testing tool. It's a a W3C protocol for remote control of web browsers. I think once you get over that misconception, selenium starts to make a lot more sense.
That is just further reason why it ought to support scenarios that the grandparent was describing, like modifying request data, even if that functionality is not useful for automated testing
Re: Prototype: Puppeteer for Firefox
#115Huh. I worked on exactly this idea as a Mozilla intern in 2017. I wrote a collection of Rust crates (mentioned in [0]) comprising auto-generated types for all Chrome DevTools Protocol messages [1], (de)serialization, and a server lib to handle both the initial HTTP handshake and subsequent command execution over WebSockets. I used that to build out an initial CDP server inside Firefox (and Servo) with support for a c…
Looks like this integration is being developed primarily by a Google employee, rather than a Mozillian ... so perhaps Mozilla is still not particularly into this idea :)
Re: Prototype: Puppeteer for Firefox
#116Anyone who wants to play around with some Puppeteer examples, I built https://puppeteersandbox.com . If you want to record your own scripts, I also am actively developing https://checklyhq.com/Puppeteer-recorder , a Chrome extension.
You misspelled the URL https://checklyhq.com/puppeteer-recorder
Love recording macros
Re: Prototype: Puppeteer for Firefox
#117Anyone who wants to play around with some Puppeteer examples, I built https://puppeteersandbox.com . If you want to record your own scripts, I also am actively developing https://checklyhq.com/Puppeteer-recorder , a Chrome extension.
You misspelled the URL https://checklyhq.com/puppeteer-recorder Love recording macros
Argh, thanks for the heads up
Re: Prototype: Puppeteer for Firefox
#118Anyone who wants to play around with some Puppeteer examples, I built https://puppeteersandbox.com . If you want to record your own scripts, I also am actively developing https://checklyhq.com/Puppeteer-recorder , a Chrome extension.
That second link is a 404, although I love your 404 page GIF =) Checkly looks like a great product!
Thanks, building a SaaS is 99% getting the 404 pages right!
Re: Prototype: Puppeteer for Firefox
#119How is the DevTools/Remote protocol better (or worse) than WebDriver prptocol for integration testing?
It's much more reliable.
I recognize your name from the Rust community. Have you checked out the rust-headless-chrome library yet? It is essentially our puppeteer, in Rust. I added the print_to_pdf feature a few months ago. I haven't touched the other functionality yet. The project isn't feature complete, yet, and also would benefit by an asyncio refactor, maybe when async-await releases.
Re: Prototype: Puppeteer for Firefox
#120Huh. I worked on exactly this idea as a Mozilla intern in 2017. I wrote a collection of Rust crates (mentioned in [0]) comprising auto-generated types for all Chrome DevTools Protocol messages [1], (de)serialization, and a server lib to handle both the initial HTTP handshake and subsequent command execution over WebSockets. I used that to build out an initial CDP server inside Firefox (and Servo) with support for a c…
Looks like this integration is being developed primarily by a Google employee, rather than a Mozillian ... so perhaps Mozilla is still not particularly into this idea :)
The Firefox end of this is being led up by :ato at Mozilla.