What happens when you combine over 1,500 real desktop and mobile browsers with the leader in AI-powered visual comparison testing tools? Simply put, an unbeatable codeless visual testing strategy.
Now it’s easier than ever to take automated browser screenshots across hundreds of different browsers with CrossBrowserTesting, and then have Applitools Eyes analyze the differences, down to the pixel level.
We’ve always thought Applitools did an amazing job with their visual comparisons, and once we investigated the solution further, we saw what a great choice it was for regression testing. We also thought we could couple our browser and device lab’s Automated Screenshot functionality with the Applitool’s Image Comparison engine to create something really special and bring consumers a faster, simpler way to produce the screenshots needed for comparison.
What is Visual Testing?
So, what is visual testing in the first place and why should you be excited about this partnership? Visual testing allows you to test that your website or web application looks correctly at the UI level. While functional testing focuses on making sure things work, visual testing focuses on making sure things look right. And it’s becoming a bigger deal!
Since different browsers will often render an application differently, visual testing is critical in cross-browser testing to make sure the actual user experience aligns with how it’s designed to look in terms of layout, text, images, etc. If a button can be clicked, but it’s nearly off the page entirely on an iPhone 6 and looks awful, this code shouldn’t go to production. But if you simply had Selenium tests or another type of functional testing, this error would be missed as it “technically” did pass our functionality test.
Previously, visual testing on multiple browsers and devices requires technical knowledge of scripting or a long manual process. However, with the CrossBrowserTesting and Applitools integration, comparing screenshot regressions is smooth and streamlined for a tester of any level — no coding necessary.
Getting Started with the Applitools Integration in CrossBrowserTesting
You’ll first need to set up a CrossBrowserTesting account and Applitools account if you don’t already have one. This will give you an API key to use once you’re in CrossBrowserTesting.
Then, when you pick your browsers, run a test under “Screenshots” in CrossBrowserTesting, and click advanced options, you should see an option to “Send to Applitools”. Click “Set” to enter your Applitools API key, pick the browsers you want to use, run the test, and that’s it! You will receive screenshots of your application in each browser, and the test will be automatically sent to Applitools where you can see each batch.
The best part is that when you run your tests again in the future, it’s easy to find the test in CrossBrowserTesting and select “Run Again” to create new screenshots that will automatically upload to Applitools and match against their earlier versions. That’s when you can go to Applitools for a visual comparison that shows passing and failing tests. These types of visual regression tests can be incredibly powerful and save hours of time writing code.
For more information on using the CrossBrowserTesting and Applitools integration, you can visit our support page here.
Happier Testing
To sum it up, here are a few reasons why the CrossBrowserTesting and Applitools Eyes integration will be your new favorite visual testing duo:
- Visual regression testing with screenshot comparisons
- 1500+ real desktop and mobile browsers
- Zero Selenium knowledge or coding skills needed
- Easy to save and easy to share test results
While CrossBrowserTesting and Applitools have exceeded expectations on their own terms, the integration will be a powerhouse for teams looking for the ultimate responsive design package. Test faster and across more browsers with no coding and maintenance with confidence that you’ll be releasing an application that will impress your users.
Hi, I have a question about applitools eyes plugins which is used to display report on Jenkins. When we configure applitools eyes plugins, what kind of data will be transferred through eyes plugins?