In the simplest terms, automation is the test code developed to reduce human efforts whenever there are any changes in the system and the system then needs to be revalidated against new changes.

In my previous article, I discussed the basic concepts of  Visual Regression Testing. Now, let's delve deeper into defining a visual testing architecture based on a business model.

Designing and writing tests aren't the most exciting things in the world, we know, but tests are absolutely essential for any app you write. They might be the difference between a shining 5-star app on the AppStore, or a bug-ridden collection of code. We all know what Unit Tests are and how to write them, but since XCode 7, Apple has introduced us to UI tests inside their IDE. With these tests, you can record a user's interactions with your app and check to see whether it's behaving as it should.

Essentially, Visual Regression is a tool for image comparison. It compares the actual page image by loading the page in real time, with a baseline saved image. If there are any pixel differences, the tool shows the result as a failure. These tools allow you to set ignored areas to work with dynamic components, thus, avoiding false negatives.

In this blog post, I will give an overview of Ansible by delving into how it works, the installation process, creating a playbook, and running commands. 

For many, manual cross-browser testing takes a lot of time and is a boring, repetitive job. Here is a practical example of how BrowserSync helps us test different browsers at the same time without any programming. In this blog, we're going to set it up and explore some good examples of where it's utilized. Here we go!

Google recently announced that the ChromeDriver now has support for headless mode, but what exactly is a headless browser? When and why should we use it? How does it differ from the standard web browsers?