by Steve Endow
I recently developed a new AppSource app for Business Central. I used GitHub Copilot (GHCP) to create a nice user guide for the app, and asked Copilot to insert placeholders for screenshots. The resulting 23 page user guide looks nice, but I discovered that it called for 21 screen shots.
Now that we've entered the age of AI and "agentic engineering", where an agent can commit and push for me so that I don't have to type or click at all, I have become impressively lazy. Naturally, it would be uncivilized for me to manually save 21 screen shots. That is sooo 2025.
While chatting with BC MVP Brad Prendergast, he sent me a post about something called Playwright. It sounded vaguely familiar to me, because it was mentioned in the book Vibe Coding by Steve Yegge and Gene Kim. I looked it up and (re) learned that Playwright is a browser automation tool.
Playwright Test is an end-to-end test framework for modern web apps. It bundles test runner, assertions, isolation, parallelization and rich tooling. Playwright supports Chromium, WebKit and Firefox on Windows, Linux and macOS, locally or in CI, headless or headed, with native mobile emulation for Chrome (Android) and Mobile Safari.
Okay, interesting.
So I ask GHCP: Can Playwright take screen shots?
GHCP: Yup.
And that is how I started a journey to spend hours building automated BC screen shot capture scripts using Copilot and Playwright.
 |
| Exactly 1280 x 720, with a specific row selected |
