defied

I’ve been using headroom to save on token usage and it’s pretty effective.

There has been the (Apple provided) safaridriver for a couple of years. It speaks WebDriver W3C and can be used to interact with a Safari instance.

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?

Physical devices for AI agents is something we at TestingBot do provide: https://testingbot.com/support/ai/mcp

Same name as the test automation framework https://nightwatchjs.org/

Looks good, excited to try this together with the CDP feature. If it works well we can add it to our (TestingBot) integration/documentation.

We created this as a free tool a while back on TestingBot: https://testingbot.com/free-online-tools/critical-css-genera....

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.

You can't use AppleID or iCloud because Apple's virtualization.framework does not support this (yet) https://developer.apple.com/forums/thread/707459

If you run macOS without the virtualization.framework, which is only possible on non-ARM mac's, then it will work.

We use it at https://testingbot.com to provide a realtime video stream of remote desktops and mobile device screens. Mostly with Pion (Go)

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.

Chrome DevTools has an experimental feature since Chrome 89 which allows you to record Puppeteer scripts as well: https://developer.chrome.com/blog/new-in-devtools-89/#experi...

not yet - though we would like to add support for Detox in the future.

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.

If you're using ffmpeg with rtp, you can use Pion to make it a WebRTC stream: https://github.com/pion/webrtc/tree/master/examples/rtp-to-w...

If you're looking for smart USB Hubs, these are pretty good https://www.cambrionix.com/

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.

We’ve recently released an option to run Cypress tests on browsers in our cloud: https://testingbot.com/blog/testingbot-cypress

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, ...

We are running a SaaS platform [1] that allows you to connect your Playwright/Puppeteer to our grid of browsers. It’s built for parallel testing.

[1] https://headlesstesting.com

I work for https://headlesstesting.com where we provide a grid of browsers, which people can use in combination with Puppeteer and Playwright. One of the reasons people use this, instead of Selenium, is because of the increase in speed.

We’re doing just that at https://testingbot.com : stream android emulators and even physical devices. You can control these through your own browser.

I’m working on HeadlessTesting.com - launched last month.

It is a grid of browsers; currently Chrome, Firefox and Edge, which can be used to run Puppeteer and Playwright scripts.

Your existing Puppeteer and Playwright scripts can be easily configured to connect to our grid. The advantage for the user is scalability, no maintenance and setup of infrastructure and support.

Usecases include generating PDFs and screenshot and headless browser testing.

Another good optimization step is to replace the JsC engine for Android with Hermes.

Self-funded and built entirely by myself: https://testingbot.com

It’s a grid of browsers and mobile devices for people to run their automated tests on.

There are quite some disadvantages to use AWS Lambda to do Automated Testing (test time is capped to 15min, cold start waiting time, ...).

The advantage is that you can run a lot of tests concurrently at a relatively cheap cost.

The company [1] I work for offers VMs that are created/destroyed automatically after each test. There's no cold start, and no time limit. Plus you can choose to run headless like Puppeteer or test in an actual OS like Win/Mac.

[1] https://testingbot.com

Placing an order does not work, due to a Javascript error I think: `TypeError: handler.open is not a function`

My company provides a similar service, with both Chrome and FireFox headless support for Automated Testing/Screenshots: https://testingbot.com/support/getting-started/headless.html

We run each test in a new VM, running on our own private cloud (dedicated servers).

Note: we use the Selenium protocol for this, not yet Puppeteer.

Because of security, we want to make sure each test can not be affected by a previous test.

If you'd run multiple tests on 1 VM, then one customer could change a property on the VM or alter a state that might cause the next test on the VM to fail.

By providing a pristine VM per test, we guarantee that each test cannot be affected by any previous test.

At TestingBot [1] we run about 50k sessions / day in real Chrome browsers (each session is a new Virtual Machine with Chrome freshly launched).

Compared to the other browsers we offer, Chrome is by far the most stable.

[1] https://testingbot.com