Topic
#playwright
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
Loot
More from this topic
Endform runs existing Playwright suites on isolated cloud runners and plugs the result into Vercel preview and production deployments. Endform is a managed Playwright test runner for Vercel teams that want deployment checks without building their own browser-runner fleet. It is useful when a suite is slow because tests run serially, collide on shared state, or need trace history across preview deployments. Vercel's Marketplace changelog says Endform can run each test on its own isolated machine, link pass/fail checks to Vercel deployments, keep full Playwright traces, and charge by test runtime. Endform's docs add the important setup caveat: tests run remotely, so the target app must be reachable by the remote runners or proxied through Endform's local-network option. Best fit Vercel apps with Playwright suites that slow down preview deploys. Teams that want deployment checks tied to traces and historical runs. SaaS products where flaky E2E tests delay releases. Projects that already use @playwright/test and want less CI plumbing. Check before using Confirm pricing and runtime limits for your test volume. Make sure each test is independent enough to run in parallel. Check how preview deployment protection, secrets, and test accounts are handled. Validate that remote runners can reach the app or configure the proxy path. Keep destructive tests away from production data.
shot-scraper 1.10 adds a practical video mode for repeatable web-app demos: write a YAML storyboard, let Playwright click through the flow, and export WebM or MP4 for reviews, changelogs, and agent handoffs. shot-scraper has always been useful for automated screenshots, but version 1.10 makes it more valuable for agent-heavy development work: the new shot-scraper video command records a browser routine from a YAML storyboard. What it does shot-scraper video takes a storyboard.yml file, launches a browser through Playwright, runs setup and interaction steps, and records the result as WebM. If ffmpeg is available, the same run can also produce MP4 with --mp4. Storyboards can define a server process, viewport, cursor display, startup waits, JavaScript setup, and scenes made from actions such as click, type, fill, press, scroll, pause, wait, open, screenshot, shell, Python, and JavaScript steps. Practical workflow Where it helps most Pull requests where reviewers need to see a UI flow without running the branch. Changelogs that need compact product clips. Regression demos for browser automation work. Agentic coding workflows where the operator wants proof of behavior, not just a generated explanation. Documentation examples that should be rerunnable from source. Caveats This is strongest for deterministic web flows. You still need stable selectors, realistic waits, and careful handling of authentication cookies or secrets. MP4 export depends on ffmpeg, and browser automation can still flake if the target app has timing issues. Source links Release notes: https://github.com/simonw/shot-scraper/releases/tag/1.10 Official video docs: https://shot-scraper.datasette.io/en/stable/video.html Project repository: https://github.com/simonw/shot-scraper Author announcement and example: https://simonwillison.net/2026/Jun/30/shot-scraper-video/
Blog