Software & DevOpsDone with Microsoft Scout 2026-10-12
Control a browser to fill forms and debug sites
A tutorial describes Scout opening sites, filling forms, clicking, uploading files, extracting page info, and reading console logs and network requests.
- What They Did
- The guide explains that Scout drives its own Playwright browser session. You describe a task in plain language, such as filling a form, checking a dashboard, or reporting console errors, and Scout decides to use the browser. It can click, type, upload files, take snapshots and screenshots, extract text, and read console logs and network requests. Sensitive actions can pause for your approval.
- How It Went
- It is a feature walkthrough, not a test report, so it gives no results or numbers. It says Scout can edit Loop documents this way. For Microsoft 365 data it prefers API tools and WorkIQ over the browser.
- Worth Knowing
- Logging in, submitting forms, and making changes may prompt for approval depending on your permission settings, which you can adjust under Settings, then Permissions.
Try it yourself with Microsoft Scout
Open [your website or staging URL] in a browser and walk through [the form or flow, e.g. signup or checkout] using test data like [sample name and email]. Click through each step, upload [test file] if there's an upload, and read the browser console logs and network requests for errors. Do not submit anything to a live production system without showing me what you're about to send first. Finish with a list of any errors, failed requests, or broken steps you found.
Do this with a skill.
These SkillShop playbooks do this exact job.