10 hours ago · 16 min read3286 words · Tech · hide · 0 comments

ℹ️ TL;DR The technical companion to part one. If your web app has a Playwright end-to-end suite, you already own most of a training-video studio. This post walks through what it takes to turn one into the other: a small helper vocabulary, an injected overlay, honest fixtures, and a build pipeline, with the lessons I picked up at each step. Part one told the story; this post is the how. The pitch, one more time for the people who came straight here: I generate silent, captioned training videos for two web applications by driving them with browser automation, and when an interface changes I rebuild the affected videos with one command. If you want to see the output first, the two libraries live at locallygrown.net/docs/videos and refreshingspaces.life/help/videos. Everything below is what you’d need to know to do the same for your own project. One insight starts it Playwright can record video of everything that happens in a browser context. Turn that option on, and every test you…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.