Free tools Windows power users keep installed
One-click scans. No signup required.
To test a site’s appearance in Safari and Chrome with Applitools Eyes, keep your existing browser automation tests, add Eyes visual checkpoints at important UI states, and configure both browsers as test environments. Eyes compares each checkpoint with a saved baseline and reports visual differences; a person reviews those differences before approving baseline changes. By default, Safari and Chrome have separate baselines.
How Applitools Eyes cross-browser visual testing works
Visual testing checks whether an interface looks as expected, alongside the functional checks your browser tests already perform. Your test suite drives the application to a relevant state, such as a loaded product page or completed form. At a checkpoint, the Eyes SDK captures the page and sends it to the Eyes server for comparison with a baseline. Results and differences are available for review in Eyes Test Manager. See Applitools’ system overview.
As an Amazon Associate I earn from qualifying purchases.
- Run the test flow that brings the site to a meaningful UI state.
- Add an Eyes visual checkpoint at that state.
- On the first run in an environment, let the captured appearance establish its baseline.
- On later runs, inspect reported differences. Decide whether each change is an intended design update or a regression.
- Save an updated baseline only after approving the change; otherwise, investigate or report the difference as a bug.
This human review matters: an image difference alone cannot tell you whether a changed button, shifted layout, or missing element was intended. Applitools explains the baseline cycle in its visual UI testing overview.
Configure Safari and Chrome in your existing test suite
Use the Eyes SDK integration for the language and framework your suite already uses. The official Selenium Java quickstart demonstrates adding desktop Chrome and Safari targets through Eyes Configuration, with viewport dimensions specified for the targets. Its sample also illustrates that browser and device targets are explicit configuration choices, including Firefox and mobile Chrome emulation.
#1 Best Overall
- 【Adhesion Range】 Quickly determine the adhesion of a large variety of paints up to 50μm (2 mils) thickness.
- 【Qaulity】 Built with streel and 11 tapered teeth with 1mm spacing.
That Java example is not a universal configuration recipe: Playwright and other SDKs have their own setup, fixture conventions, and APIs. Follow the current instructions for your selected SDK rather than copying Java syntax into another framework. For Playwright, see Applitools’ Playwright integration, which uses an Applitools-enhanced test fixture and describes match-level configuration.
Keep local browser setup aligned
For the local Selenium Java setup documented in the quickstart, the ChromeDriver major version should match the installed Chrome major version. Treat this as guidance for that documented setup, not as a universal Safari-driver instruction: the cited materials do not establish one Safari driver procedure that applies across frameworks.
Choose separate browser baselines or a shared comparison deliberately
By default, a baseline is associated with the application name, test name, operating system, viewport size, and browser. A Chrome run and a Safari run therefore ordinarily have distinct baselines. This is useful when the goal is to confirm that each browser retains its own accepted appearance, rather than treating every browser-specific rendering difference as a regression. Applitools describes these baseline identifiers in its baseline help article.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, 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 minuteRank #2
- Compatible with 3 different connector types:RJ11/RJ45/BNC,used to test the detachable module of two remote points.
- 300 feet test distance (RJ-45/RJ-11/BNC).Ergonomic portable handheld design.Powered by 9V alkaline battery (not included).Convenient battery access.
- BNC terminator 25/50 ohm indication.Straight line or cross indication.The LED indicates the connection and failure of wires and pins.RJ-11/RJ-45 is equipped with 50u gold plating.
- Straight line or cross indication.The LED indicates the connection and failure of wires and pins.
- Simple one-click test.Quick test.High quality guarantee.
Applitools also documents a Baseline Environment Name option for cross-environment comparison. Its cross-environment help article, published in 2021, recommends the Layout match level because environments can differ visibly. Since that guidance is older, check the current documentation for your SDK before relying on a particular setting or syntax.
- Use per-browser baselines when you want Safari and Chrome validated against their separately approved appearances.
- Consider cross-environment comparison only when you intentionally want a shared reference and have accounted for browser and environment rendering differences.
In either model, review diffs for each browser before approving an update across the matrix.
Choose local browsers or cloud rendering based on the coverage you need
Local browser execution runs the browsers in your own test environment. Applitools also describes Ultrafast Grid as a cloud browser and device rendering option that works with existing Playwright, Cypress, Selenium, and Appium suites; see its cross-browser testing page. The sources establish these as alternative coverage approaches, but do not provide independent comparative performance data. Choose based on your framework’s supported integration, the operating systems and viewports you need to cover, and the amount of baseline review your team can manage.
Applitools’ product page includes claims such as “up to 99%” lower flakiness and rendering across hundreds of combinations. Those are vendor claims, not independent measurements, so they should not be treated as expected results for every suite.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Keep checkpoints stable and useful
- Choose checkpoints that represent meaningful states in the user journey, not arbitrary moments while the page is still changing.
- Keep the target viewport and other environment settings intentional and consistent; viewport size and operating system are part of the default baseline identity.
- Review Safari and Chrome differences in their browser contexts when using separate baselines. A change accepted for one environment is not automatically an approval for the other.
- Use your SDK’s documented match-level and fixture conventions. The exact APIs differ by integration.
Troubleshooting common setup problems
Chrome tests fail to start locally
In the Selenium Java local setup, check that ChromeDriver’s major version matches Chrome’s major version, as required by the quickstart. This specific advice does not establish a fix for every driver or framework configuration.
Safari and Chrome show different results
First check whether the tests are using separate baselines, which is the default behavior because browser is part of the baseline environment. If you intended a shared cross-environment comparison, review the Baseline Environment Name configuration and consult current SDK guidance on match levels.
Rank #4
A checkpoint reports visual differences after a design change
Open the result in Eyes Test Manager and review the affected areas. Approve and save the new baseline only if the change is intended; otherwise, investigate the UI regression or report it as a bug.
The setup instructions do not match your framework
The concrete browser-target example cited here is for Selenium Java. Use the dedicated setup for your language and framework. For Playwright, Applitools documents its enhanced fixture and integration-specific conventions in the Playwright integration guide.
Using Applitools MCP with an existing Eyes suite
Applitools’ MCP Server documentation says that setup and checkpoint-creation tools currently support only the Playwright Fixtures SDK. Inspection, resolution, and review tools can work with Eyes results created by any SDK. This is a limitation of those MCP tools, not a general restriction on which SDKs can use Eyes.
Best Value
Or skip the browser setup
For a standalone page image rather than a visual-regression test suite, ScreenshotNeo offers a screenshot API. It is not a replacement for Eyes baselines and review. One GET request returns an image or PDF; for example:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Before capture, it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The Free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently Asked Questions
Can Applitools Eyes test Safari and Chrome in the same automation suite?
Yes. Configure both browser targets in the Eyes setup for your language and framework, then add visual checkpoints to the suite’s test flow.
Does Applitools MCP setup support every Eyes SDK?
No. Its setup and checkpoint-creation tools currently support only the Playwright Fixtures SDK, while inspection, resolution, and review can work with results from any SDK.
Quick Recap
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.
