For walkthroughs, QA evidence and bug reports
Get a picture of every step in a user flow
Run a flow of clicks and typing and get a screenshot before the first step and after every step that completes.
The problem
A bug report that says "checkout broke" is not much to go on. Neither is a QA sign-off with no evidence, or an onboarding guide whose screenshots were taken by hand in an order the product no longer follows.
How domscout handles it
With captureTimeline on, the request takes a screenshot before the first action and another after each action that completes, and returns them in order in timelineBase64, next to the per-step results in actionResults. Flows like this can outlast a direct request, so send async: true and collect the frames from the job when it finishes.
Where it shows up
- Step-by-step images for an onboarding guide.
- Evidence attached to a QA sign-off.
- A bug report that shows exactly where a flow went wrong.
The request
POST /screenshot. Timeline capture starts at Business and adds 2 credits, so this request costs 3. With async: true the response is a job, and GET /job/{jobId} returns the frames when it finishes.
Go further
More in Testing and QA: Responsive layout checks · Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.