Curious how they frame testing on real devices: “Real devices on demand: spin up iOS simulators and Android emulators”. So those are not real/physical devices?
It uses a remote browser to start a Puppeteer session and runs JavaScript code to extract the critical CSS needed for above-the-fold content. We chose Puppeteer because it’s fast to instrument the browser and works well even on JavaScript-heavy sites.
I’m working on a project that provides remote browsers, running on VMs/containers, capable of running Playwright tests (and Puppeteer scripts): https://headlesstesting.com/
We’ve seen a consistent growth of interest in people wanting to use Playwright for browser automation (and testing).
For testing purposes, you can achieve similar results with Selenium IDE. You can export tests and upload these to (our website) https://testingbot.com - supports screenshots and scheduled runs.
Would using gstreamer instead of ffmpeg offer better or worse performance? (Less CPU usage on the sender side?) If anyone has experience with this setup, I’d love to know.
At https://testingbot.com we use this to install apps, take screenshots and manage devices for our users running tests against our physical iOS devices.
If anyone knows how to improve the graphics performance on Windows, please share. Compared with other hypervisors like Virtualbox or ESXI, there’s no graphics driver for Windows VMs with QEMU.
We're using the "PowerPad" hubs for mobile device hosting. Each of the ports on the USB hub will detect the device and deliver its fastest possible charge.
Interesting article. I operate a somewhat similar service at https://headlesstesting.com where we provide a grid of headless browsers. You can connect to these via Puppeteer (and Playwright) to do various things discussed in the article: scraping, taking screenshots, generating PDFs, ...