Applitools Eyes

What do you like best about the product?

Once everything is set up, it’s easy to monitor our tests.

What do you dislike about the product?

The UI is not really user friendly on certains parts of the website

What problems is the product solving and how is that benefiting you?

the amount of time we are currently doing manual testing

What do you like best about the product?

I really appreciate Applitools' AI-powered visual testing capability. It automatically detects UI differences that traditional Selenium functional tests often miss, such as layout shifts, font changes, color inconsistencies, and alignment issues. The seamless integration with Selenium and TestNG reduces manual validation effort. I also find the clear dashboard provided by Applitools very useful for reviewing and approving visual changes, which makes regression testing faster and more reliable. Setup was fairly easy for us since we were already using Selenium with Java and TestNG, and integrating Applitools into our existing automation framework was straightforward. Once we created the initial baselines, maintaining the visual tests became much easier.

What do you dislike about the product?

Applitools has been a great tool overall, but there are a few areas that could be improved. The initial setup and baseline management can be a bit complex for new users. Handling dynamic content often requires additional configuration, such as ignore regions or match settings, to avoid false positives. The pricing may also be a challenge for smaller teams. Additionally, I'd like to see improvements in test execution speed and more detailed diagnostics when visual tests fail to make troubleshooting even easier.

What problems is the product solving and how is that benefiting you?

I use Applitools for visual testing, enhancing regression test quality by detecting UI issues missed by functional tests. The AI reduces maintenance effort and false failures. It integrates well with Selenium and TestNG, but the setup and dynamic content handling can be tricky. Pricing can be high for small teams.

What do you like best about the product?

The way it can simplify stacks of validations and just effortlessly condense every UI check into a single simple screenshot comparison. Also it provides a very useful comparison view/UI for you to go over the changes in detail.

What do you dislike about the product?

The save functionality could be snappier, it is a small detail but it can compound fast when reviewing multiple batches

What problems is the product solving and how is that benefiting you?

Its lowering spec complexity and maintenance by adding visual validations to our pipeline. Reducing Developer and QA time to debug and figure out what is going on or if the changes are actually expected or not

What do you like best about the product?

Smart visual comparison tool, and it’s easy to ignore or lay out specific regions directly from the code.

What do you dislike about the product?

Sometimes we run into issues with baselines. After a merge, the next PR can fail even though we already approved the updated baseline.

What problems is the product solving and how is that benefiting you?

We don’t have a dedicated QA team, so we use Cypress, but we still need visual testing for our system. It’s also really helpful when we’re updating some npm packages.

What do you like best about the product?

I use Applitools for visual testing automation. It primarily solves regression testing issues for me, and I also use it for pipeline automation without the need to develop code, which is great for coding. I like that Applitools is easy to use, and the results are really nicely displayed. It's very useful that you can set and configure anything with the image comparison. The initial setup was super easy, and compared to using automation with Playwright, Applitools makes it a lot easier to deal with changing applications.

What do you dislike about the product?

nothing

What problems is the product solving and how is that benefiting you?

I use Applitools for visual testing automation. It solves regression testing, pipeline automation, and avoids code development. It's great for autonomous coding. Applitools made it easier compared to playwright, especially with Dynamic applications.

What do you like best about the product?

I find it good because it was roughly easy to Integrate with it.

What do you dislike about the product?

Some of the metrics for the usage were blurry.

What problems is the product solving and how is that benefiting you?

I could say about Applitools team which helped me with the integration. I helped me better understand it and most specifically Pavan Savlani who was very helpful and willing to help me.

What do you like best about the product?

Applitools’ Visual AI engine was invaluable for us because it consistently caught real layout regressions across different browser configurations without drowning us in false positives. Since it evaluates the UI more like a human eye rather than relying on brittle pixel-matching, it significantly reduced our test maintenance overhead. As a result, we felt much more confident shipping frontend updates faster.

What do you dislike about the product?

I honestly struggle to find any real flaws with the platform itself. If I had to point to a challenge, it was simply the initial mindset shift of learning to trust a visual AI instead of our legacy testing methods. Once I got past that short adjustment period, it worked exactly as promised.

What problems is the product solving and how is that benefiting you?

Applitools addresses the flakiness and high maintenance that come with traditional visual testing, especially when it relies on pixel-by-pixel comparisons and brittle DOM assertions. By intelligently automating UI checks across multiple browsers and screen sizes in one go, it removed hours of manual visual QA from our process. In the end, it helped us speed up our release cycles while still maintaining visual consistency at scale.

What do you like best about the product?

The standout capability for me is the Ultrafast Test Grid (UFG). It lets us scale visual tests smoothly across multiple desktop browsers, different viewport sizes, and mobile devices at the same time. As a result, we get broad responsive coverage right away without needing to build, host, or maintain a complex internal testing infrastructure.

Integrating the SDK into our existing automation framework was very straightforward and felt like a quick win for the team. On the execution side, being able to switch between Layout and Dynamic matching modes keeps our visual assertions highly stable and effectively removes the flaky false positives that are usually caused by dynamic data or shifting content. The Root Cause Analysis (RCA) feature is also exceptionally precise: when a mismatch happens, it points directly to the specific DOM changes or element displacement in the code, saving our developers hours of debugging time.

The Applitools support team is exceptionally responsive and proactive. Our weekly collaboration sessions have been invaluable, allowing us to quickly clarify technical queries and resolve roadblocks. This high-touch support has directly helped us build a highly robust, scalable testing framework for our responsive web applications in quick time.

What do you dislike about the product?

While the platform is highly efficient, there are a few notable gaps in the administrative and reporting tools. Right now, there’s no native option in the Applitools dashboard to set up automated alerts for usage thresholds when our team reaches a specific consumption tier, which makes proactive budget tracking difficult. In addition, the dashboard doesn’t provide a granular view of usage metric for example, a breakdown showing which specific pages are consuming our monthly license quota. Having a more detailed metrics dashboard would give us much better visibility and help us align the test suites we build with the actual resource consumption reflected on our monthly invoice. Finally, optimizing the initial test configuration for complex responsive layouts takes time.

What problems is the product solving and how is that benefiting you?

We struggled to verify responsive layout consistency across an ever-growing matrix of browser versions and mobile viewports. Manual checks were too slow, and pixel-matching tools failed constantly because of minor rendering differences. Applitools Eyes addresses this by shifting the focus to AI-driven validation using DOM-based and different visual modes.

The centralized dashboard has also unified our workflow by enabling developers, QA testers, and Product Owners (POs) to collaborate in one place. We can review baseline changes and sign off on visual deployments together. This cross-functional visibility helps ensure design consistency across all form factors, while keeping our release cycles fast and predictable and allowing us to catch regression leaks early when visual changes slip in.

With UFG, we’re able to test many different combinations at once, very quickly, without needing to set up the infrastructure. As a result, we save time and effort.

What do you like best about the product?

AI Intelligence , Support, Adoption for customer requirement and Integrations with SDK kit and Initutive UI.

What do you dislike about the product?

Applitools could improve its notifications for the emailable report after comparisons. I would like more detailed English sentences that clearly explain formatting, font, and other visual differences, along with the RCA category and the AI recommendations.

What problems is the product solving and how is that benefiting you?

Visual testing and PDF comparison for both content and visuals.

What do you like best about the product?

The platform has many useful features, such as layout regions. UFG is also a strong feature. It’s good to see that they’re moving toward AI code generation using MCPs.

What do you dislike about the product?

the platform has so many feOne area that could be improved is baseline image maintenance. As the number of visual tests grows, managing and updating baselines can become time-consuming, especially when there are expected UI changes across multiple tests.

Additionally, Applitools offers many powerful features, but there is sometimes a communication gap around new releases and capabilities. At least for my team, we are not always aware of newly introduced features or best practices unless we actively look for them. More proactive communication, release summaries, in-product announcements, or feature walkthroughs would help teams discover and adopt new functionality more effectively.
atures. But some times I

What problems is the product solving and how is that benefiting you?

We use Applitools primarily for Visual Regression Testing (VRT). It helps us automatically detect unintended UI changes across our applications, allowing us to identify visual defects early in the development cycle before they reach production.

This has improved our confidence in releases, reduced the need for manual UI validation, and helped us catch issues that traditional functional automation might miss. Overall, it has contributed to better software quality while saving time and effort during regression testing.