Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsTo test responsive breakpoints with Applitools, identify the transition widths in your own CSS and design requirements, then run visual checkpoints at fixed viewport sizes just below and above each transition. Compare each result with an appropriate baseline, investigate differences, and update baselines only after review. There is no universal set of breakpoint widths that fits every site.
How do I test responsive breakpoints with Applitools?
- Find the breakpoints that matter to your site. Read the application’s CSS and design requirements. For a transition at width
W, test widths immediately below and aboveWto catch changes such as navigation collapse, text wrapping, overflow, or grid rearrangement. Add other widths where the design requirements call for distinct layouts. Common device labels such as “tablet” or “desktop” are not a substitute for the actual transition points. - Choose fixed viewport dimensions. Set both width and height for each case where your SDK supports it. Keep the browser, operating system, and viewport consistent when comparing against a baseline; these environment details can affect the visual result. Add other browser engines as separate coverage rather than treating them as replacements for tests at breakpoint boundaries.
- Drive the page to the state you want to verify. Complete navigation, data loading, or other setup before taking the visual checkpoint. Use a full-page capture if below-the-fold content is relevant; use a focused region for a component-level check.
- Choose a match level for the comparison. Use Strict when appearance should remain stable in a specified environment. Consider Layout when content or styling may vary but element positions and presence should remain sound.
- Review the differences. Decide whether each change is an intended design update or a defect. Accept an intentional change as a new baseline only after reviewing it; a baseline update records the accepted appearance, but does not establish that the design is correct.
Applitools’ responsive-design page describes capturing mobile, tablet, and desktop views in one test and running comparisons across browsers and viewports with Ultrafast Grid. These are Applitools’ product capability descriptions, not a guarantee of a particular speed or outcome for your project. See Applitools responsive web testing.
Set up a Playwright visual checkpoint
The following example uses the Applitools Playwright fixture and eyes.check() pattern documented by Applitools. Confirm the installation and API details for the SDK version in your project in the Playwright integration documentation.
import { test } from '@applitools/eyes-playwright/fixture';
const breakpointCases = [
{ name: 'just-below-breakpoint', width: 767, height: 900 },
{ name: 'just-above-breakpoint', width: 769, height: 900 },
];
test.describe('responsive navigation breakpoint', () => {
for (const viewport of breakpointCases) {
test(`${viewport.name} (${viewport.width}px)`, async ({ page, eyes }) => {
await page.setViewportSize({
width: viewport.width,
height: viewport.height,
});
await page.goto('https://example.com');
// Replace this with an app-specific readiness condition when possible.
await page.locator('body').waitFor();
await eyes.check('Responsive navigation', {
fully: true,
});
});
}
});The example’s 767px and 769px values are illustrative only; replace them with widths derived from your site’s breakpoint. The Playwright documentation also describes match-level and ignored-region options. Use an ignored region only when a known dynamic area should not determine the comparison; do not mask a region simply to silence a meaningful layout difference. Applitools lists other integrations, including Cypress, Selenium, and WebdriverIO, in its SDK and integration catalog; API behavior and configuration can differ by framework and version.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Choose Strict or Layout matching
| Match level | What it emphasizes | When it fits |
|---|---|---|
| Strict | Visible differences in text, font, color, graphics, and element position, while attempting to ignore rendering variation that does not affect human-perceived appearance. | Regression checks for a specific browser and operating system when content is mostly static. |
| Layout | Relative position and presence of elements; content and styling differences are ignored. | Pages with dynamic content or localization, or comparisons across environments where arrangement matters more than exact appearance. |
These descriptions follow Applitools’ match-level guidance. Select based on what the test is intended to protect: Layout can overlook a meaningful style regression, while Strict may flag expected content or rendering changes.
Why does my test fail to set the viewport size?
Applitools’ support guidance explains that Eyes.open aims to set the inner browser viewport, while generic window-sizing methods may size the outer window, including browser chrome. A requested size may fail if it exceeds the available display or is unsupported by the browser. That troubleshooting article dates to 2019, so verify the behavior and syntax against your current SDK and runner configuration: Why does my test fail to set the viewport size?
- Requested dimensions exceed available screen space: reduce the viewport or use a runner/display configuration that supports the target dimensions.
- Outer window is being sized instead of the viewport: use the sizing mechanism recommended for your Applitools SDK and framework; account for browser chrome when diagnosing the actual content area.
- Browser minimums or unsupported dimensions: try a supported size above the browser’s minimum and confirm the resulting inner viewport.
- Appium reports a maximized mobile window: inspect the actual runner and device viewport rather than assuming a desktop-style resize has taken effect.
- Windows display scaling changes the effective dimensions: verify scaling and the viewport reported by the browser in the test environment.
After correcting the viewport setup, rerun the test before treating the image difference as a CSS defect. Record the browser, operating system, viewport width, and height with the result so the baseline comparison has useful context.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need a screenshot rather than an Applitools baseline workflow, ScreenshotNeo can capture a page through one GET request. It is a screenshot API and MCP server for developers, not a replacement for Applitools’ baseline review and match-level workflow.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for available parameters. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and its free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000. Sign up for free ScreenshotNeo screenshots.
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.
