Free tools Windows power users keep installed
One-click scans. No signup required.
To stop a changing date from causing an Applitools Eyes visual diff, either mark the date element as an ignored region or use Dynamic matching if the date should remain visible and its surrounding appearance should still be checked. In Playwright, pass a locator for the date element in ignoreRegions. Keep that locator narrowly scoped: Eyes will not detect visual defects inside an ignored area.
Choose how Eyes should treat the date
The right approach depends on what the visual checkpoint is meant to verify. Masking is not a universal fix: it trades sensitivity to changes in the masked content for fewer diffs caused by expected variability.
| Approach | What the visual test checks | Best fit | Trade-off |
|---|---|---|---|
| Narrow Ignore region | Content and layout outside the ignored bounds | The date and its local appearance are irrelevant to this checkpoint | A visual defect wholly inside the bounds can go unnoticed |
| Dynamic region or Dynamic Match Level | Other visual content, while supported variable patterns can differ | The date should remain represented in the UI, but its value changes | Pattern recognition depends on the format and current SDK or product configuration; verify it for your test |
| Layout Match Level | Element structure and relative positions | Broadly changing content is unimportant, but layout is important | It can miss meaningful text and graphic changes across the checked area |
| Strict | Text, graphics, colors, and positioning, subject to Eyes matching behavior | The date should be stable or its visual change matters | An expected date change can produce a diff |
Eyes documentation describes Exact matching as pixel-to-pixel comparison and unusually sensitive, rather than a typical choice for ordinary verification. Match-level names and availability can vary by integration, so check the documentation for the SDK and product surface used by your test.
Ignore a date with Playwright
The official Applitools Playwright integration documents ignoreRegions on eyes.check() and shows a Playwright locator as the region. Replace the example selector with a stable selector for the date in your application:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitches#1 Best Overall
await eyes.check('Homepage', {
fully: true,
matchLevel: 'Strict',
ignoreRegions: [page.locator('.dynamic-content')],
});For example, if the date is rendered in <time data-testid="report-date">, use page.getByTestId('report-date') as the locator. The selector must match the actual date element; .dynamic-content above is only the documented example shape, not a universal date selector.
Keep the ignored bounds tight
- Target the smallest element containing the changing date, rather than a parent container that also includes a heading, status, or controls.
- Check the rendered bounds: padding or a broad selector can mask nearby labels, borders, icons, or spacing changes.
- Make sure the locator resolves reliably at the checkpoint. If the date is conditionally rendered, wait for the relevant page state before calling
eyes.check().
An ignored region suppresses comparison within its bounds. If the date is only one changing part of a larger component, ignoring the entire component may hide defects you still want the checkpoint to catch.
Rank #2
When to use Dynamic matching instead
Use Dynamic matching when a date changes but its presence and broader visual treatment should remain under test. Applitools’ product notes dated June 8, 2026 say Dynamic Match Level became the default for new Eyes tests and describe recognition of dynamic content, including date patterns. The notes also describe tolerating horizontal and vertical shifts in surrounding elements caused by dynamic content. That dated default statement does not establish that existing tests automatically changed; inspect the setting for the test you are maintaining.
Applitools’ July 8, 2026 product notes say Dynamic Match Level became the default for new Autonomous tests. They list six predefined pattern types—dates, emails, links, numbers, currency, and input fields—and support for custom regex patterns. These are vendor release statements; they do not guarantee recognition of every locale, date format, or application-specific string.
Confirm the pattern in your test
- Check the SDK and product surface used by the test, and confirm that Dynamic matching is available and enabled for that test.
- Run the checkpoint with the actual date format and locale used by the application.
- Review the resulting comparison to verify the date is tolerated while unrelated changes remain visible.
- If the format is nonstandard, consult the current SDK’s pattern support and use a custom regex where available; do not assume a pattern works without checking its behavior in the test environment.
Keep semantic date checks separate
A visual match does not prove that the date is correct. If correctness depends on a particular value—for example, a date calculated from test input—assert that value in the application test as well. You can let visual comparison tolerate an expected changing string while a functional assertion checks the actual date, its format, or the rule that produced it.
Understand broader match settings
Strict is intended to detect human-noticeable changes in text, font, color, graphics, and element position. Ignore Colors retains Strict-like checks while allowing color differences. Layout focuses on relative element positions while ignoring content differences. These modes are broader than masking one date: choose them only when their wider comparison behavior matches what the checkpoint must protect.
Ignore Vertical Shifts is a separate setting for shifts caused by changed content elsewhere; Applitools says Layout automatically ignores vertical shifts. It does not decide how the date element itself should be compared. For one irrelevant date, a tightly scoped Ignore region is the more targeted choice.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Practical troubleshooting
The date still creates a visual diff
- Confirm that the locator in
ignoreRegionsmatches the element actually rendered at checkpoint time. - Check whether the date is split across multiple elements; the ignored region must cover the changing content.
- If using Dynamic matching, verify the setting for this existing test and confirm the actual format is recognized. New-test defaults do not establish that an older test has the same configuration.
Nearby content stops being checked
Narrow the selector to the date element instead of its containing card or section, then review the region bounds in the comparison. A larger ignored area makes more potential regressions invisible.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The date passes visually but is wrong
Add or retain a functional assertion for the expected date value or calculation. Ignore and Dynamic matching control visual comparison; they do not establish application correctness.
Or skip the browser setup
ScreenshotNeo is a screenshot API and MCP server, not an Applitools Eyes replacement: it captures pages, while Eyes provides visual test comparison. For a standalone screenshot of a page, one GET request can return an image or PDF. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners before capture 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 in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Sign up for ScreenshotNeo free: 1,000 screenshots a month, no card required.
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.
