Applitools Reviews

The ability to have a comprehensive test suite built in a matter of minutes that covers more of the application then a tester could ever imagine.

The only challenging part about Applitools is at times we have false failures on very little pixel deviations.

The accuracy of the Applitools is the best in the market. The simplicity in writing the tests. The wide range of features.

The dashboard is a bit confusing for new users but with time it becomes habitual

I do not require to write a lengthy code to validate the existence of fields and the data, its as ways as a snap.

I haven't come across one yet but I am sure they are improving with every release

Applitools Eyes a tool easy to use, in a few minutes you can have a visual test. With Applitools Eyes is possible to make functional tests as well. I use Applitools Eyes each day for my test in differents program languages, Java, JavaScript, C#, and it supports my favorite testing tools Selenium, Cypress, WebDriverIO, Appium.

I have been using Applitools Eyes for testing in my own and company projects for 15 months, and so far, I haven't found something that not likes me. I love this tool.

Applitols AI tool follows certain steps in order to validate that screens or pages has not changed. It’s a great substitute for traditional way of testing , Applitols does not require advanced knowledge of programming language so even junior tester can handle it. The biggest advantage of Applitools it’s compatible with many programming languages and platforms.

Does not require advance knowledge of programming languages. Provide great and easy to understand documentation for different platforms and programming languages.

The way it compares and publish diff between benchmark and output is really impressive

I did not think there is any cons as such.

It helped me to simplify Selenium tests of my web app. I got rid of all assertions and now, I take only screenshots after specific actions. The solution is smart enough to flag only a relevant differences between baseline and screenshots from test runs as defects and I can even choose that certain parts of the web page will be ignored.

I struggle a bit to understand how I can give the test suites the name of my choice and how are the test runs marked by Applitools Eyes.

The tool was really easy to setup. The documentation was all up to date, and incorporating it with both cypress (Javascript) and selenium (ruby/java) was very easy. The tool itself is very easy to use and on to existing automation tests or newly created ones. I also thought the applitools web portal was well thought out and easy to use.

My only con though I don't think there is a way around it is when a section of the page does change and it is intended, you have to log into the Applitools web portal and flag the new failure as the new 'default' image. I don't really see any other way around that but if you are working on something that is constantly changing, know that you will need to continually update the tests. There are ways to target certain areas to check (which is a big plus) to make this less painful.

It is really easy to understand the product and it provides great features to do visual regression testing

I did not find any cons as such till now

My favourite part of testing with Applitools Eyes was the amount of code I ended up writing. For instance - in order to test a form, there's a surprising amount of code that needs to be written using other tools, with Eyes I could just take a snapshot of the form and compare it visually. Less code to maintain is always better :)

I was trying to check our (highly dynamic in terms of content) home page with Eyes and unfortunately I've has some false alarms here and there. But if the content is not *as* dynamic (that is - not changing in terms of photo/size on every page load) it's a great tool.

1) Excellent Match Level algorithms which reduced lot of assert codes in traditional way. 2) Drastically reduce maintenance of code 3) Automation Suites sync with application rapid changes 4) Pricing models are so economical 5) Easy integration with saucelab and Cloudbees (Jenkins) 6) Quick Support

1) Difficult to understand Javascript documentation 2) Need more examples for Javascript implementation 3) TestResult object behave differently with a check failed, this leads more coding to generate custom reports 4) Need more examples in Test Reports

Applitools Eyes helps speed up my automated testing process by making tests faster to writer and results easier to see. I enjoy the tools on the dashboard that allow me to ignore certain areas when comparing diffs.

The software can sometimes be tricky to use if you are not that well versed in Cypress or other testing tools. I often see a delay in running a test and seeing the results. Sometimes, results don't appear even after ensuring my api key is correct.

One line of code can replace a lot of traditional assertions (10+). How? By comparing full or partial snapshots of your AUT against a baseline. But the beauty comes in defining what to ignore (e.g. regions, dynamic content) and what to focus on (only text, text + font, relative/absolute position). All of these are so hard to account for in a traditional approach yet so easy to do in the new "modern" way. Works with JIRA & Jenkins and has many more integrations.

As a coder, transitioning into Eyes Dashboard to decide upon the result will make you feel that the scripts are incomplete. The Assert layer will be done outside of the automated test scripts, which requires a different approach on getting the final Test Report.

Easy to use and by setting the baselines it helps a lot comparing the visuals rather than text. It is as easy as pie to integrate with your current test automation scripts. And like the idea of writing something with Eyes.Open() and Eyes.Close() it's something like you're asking a robot to verify if everything goes OK or not.

For a dynamic screen like a mobile game, because all objects are dynamic it's hard to locate and hard to use visual localizers. Because the tool providing so many elegant solutions, it is just one that I can say they can improve, others work perfectly.

The software is very well documented and easy to get up and running in no time.

It's not free, but most good things aren't free in life :-)

Its powered with Ai.So its pretty cool.Unlike other testing frameworks applitool is very easy to use.Because no need of heavy coding and it takes only less time.All ui defects can be found easily using this simgle tool.

What i didnt like is jumping from code to applitool dashboard.

You can use this to test the objects in a web page that do not have any other way of identification to test them. Also, you need not write a lot of assertions since you can do a lot of them at once using visual validation.

I feel it is a bit slow in execution. The concept is new so it requires a bit of usage to feel ease with it.

Applittols Eyes is the the market leader solution related to Visual Regression Testing. It allows you to detect many problems in the application, that a functional test would not be able to identify. Also, it has a great documentation, with integrations with many different programming languages and frameworks.

Considering that it is still a new technology and solution, it has a price to use that is some cases, it not easy to afford.

it decreases the number of code lines, saves time, cost, and effort

Setup confused me a little, nothing else

The ease of debugging and knowing why your test fails is on point. The visual integration is perfect for any system.

There is a lot going on in the dashboard which i would appreciate being improved in the future and later versions to prioritize what matters most and what should have priority in the dashboard.

I was blown away how easy it was to setup and get running.

Probably finding tutorials, some of them talked about same thing but each gave different steps to achieve.

The ability to compare screenshots simply is really helpful with certain types of tests, particularly those that are not easily written with selenium.

If you are not doing very specific testing, this tool is not useful. You don't need to use it for most tests.

I participated on a contest using the tool, it was really cool to understand some concepts of testing with it and seeing it working.

I did not had much time using the tool to know any cons.

I really like the way I can inspect the test results in a friendly dashboard and the support for multiple languages and frameworks.

Time execution is slightly increased in environments that do not have best processing capacity :P

- ease of use - documentation - value out of product - dashboard

- There is no cons i see as of now for Applitools