To test multiple pages with Applitools Eyes as one reviewable run, add a named visual checkpoint to each relevant page state, give related tests the same batch identity, run the suite, and review the grouped tests and comparisons in the Applitools dashboard. If Playwright runs tests in parallel, pass an explicit, stable batch ID to every worker; separate worker processes do not share ordinary global variables, so relying on process-local state can split one logical run into multiple batches.
What a batch does—and what it does not do
A batch groups related test results for review. It is not itself a multi-page capture: your existing browser test framework still navigates to each page and establishes the state you want to inspect, while an Eyes checkpoint captures that state. Inside the batch, you can review individual tests and their checkpoint comparisons.
As an Amazon Associate I earn from qualifying purchases.
Think of the structure as a suite or run containing tests, with one or more named visual checkpoints in each test. For example, separate tests might cover a product listing, a product detail page, and a checkout state. Give the checkpoints names that identify the page or component so a reviewer can tell what each comparison represents.
Recommended Free Tools
Set up page-level checkpoints and a shared batch
- Use your existing browser automation. Navigate to each page and perform the actions needed to reach the intended UI state.
- Wait for a stable state. Wait for the application condition that matters before capturing; a page-load event alone may not mean that asynchronous page content is ready.
- Add a named Eyes checkpoint. The Playwright integration uses
eyes.check()for a visual checkpoint. Configure the batch at the suite or test configuration level; the Playwright fixture documentation describeseyesConfig.batchfor BatchInfo. - Use the same batch identity for tests meant to be reviewed together. Keep unrelated runs or groups distinct, and use a unique ID for a distinct batch where appropriate.
- Run the suite and check the dashboard. Confirm the intended tests appear together in the batch and inspect their individual checkpoint results.
The precise setup around the fixture, imports, and BatchInfo can vary by SDK and version. The configuration facts here are specific to the Applitools Playwright fixture documentation; do not copy older snippets for JavaScript or another language without checking the API for the SDK you have installed.
Choose checkpoint scope and comparison settings
Configure each checkpoint for what the test is intended to verify. The Playwright integration supports full-page capture, a named checkpoint, a region, match levels, and ignored regions. For example, use full-page capture when content below the fold is part of the requirement; use a region when only a particular element or area matters. Dynamic content may require special handling, and the match behavior should fit the assertion rather than being applied identically to every page.
Stable names make review more useful: identify the page or component and, when necessary, the state being checked. After a run, open the batch, review test statuses, and compare baseline and new images at the checkpoint level. Inspect differences before changing baselines so an intended UI change is not mistaken for a regression.
Keep parallel Playwright runs in one batch
Playwright workers can run in separate processes. Ordinary global variables in one process do not automatically provide a shared batch identity to the others. If workers each construct a different identity—or fail to receive the same configured identity—the dashboard may show multiple batches for what the team considers one run.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Choose one stable batch ID for the logical run.
- Make that ID available to every worker through shared test configuration or another mechanism that crosses process boundaries.
- Configure each worker’s Eyes setup with that same identity, rather than generating a worker-specific ID.
- After execution, inspect the batch list and confirm the results are grouped as intended.
The underlying split-batch explanation is also described in an Applitools Playwright article published April 19, 2022. Its conceptual warning remains useful, but validate code and framework behavior against your current Playwright and Eyes SDK versions.
Framework and version considerations
Applitools lists SDKs for Playwright, Selenium, Cypress, WebdriverIO, and other frameworks. Choose the integration that matches the browser framework and language already used by your team. Before implementing batching, verify three things in the official documentation for that integration: the current way to configure a batch, how its identity reaches parallel workers, and whether its checkpoint controls cover your full-page and dynamic-content needs.
The available guidance does not establish one batching snippet as interchangeable across SDKs. Keep implementation instructions specific to the framework and SDK version in your project, and verify syntax against the current official docs.
Rank #4
Or skip the browser setup
For a screenshot of one URL without configuring an automated browser test, ScreenshotNeo offers a screenshot API. This is a capture option, not a substitute for Eyes batches, baselines, or visual-regression review. Its API accepts one GET request with a URL and can return an image or PDF; see the ScreenshotNeo API documentation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutecurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Quick Recap
Best Value
ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. See ScreenshotNeo or sign up for 1,000 free screenshots a month, with no card.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
