Skip to content →

Things to consider when running visual tests in CI/CD pipelines: Azure Devops & GitHub Actions

In this 3 part series Jessica Deen covers things to consider when running visual tests in CI/CD pipelines.

Things to consider when running visual tests in CI/CD pipelines: Getting Started (Part 1)

Things to consider when running visual tests in CI/CD pipelines: Azure Devops & GitHub Actions (Part 2)

Things to consider when running visual tests in CI/CD pipelines: Container Pipeline Edition (Part 3)

Testing – it’s an important part of a developer’s day-to-day, but it’s also crucial to the operations engineer. In a world where DevOps is more than just a buzzword, where it’s become accepted as a mindset shift and culture change, we all need to consider running quality tests. Traditional testing may include UI testing, integration testing, code coverage checks, and so forth, but at some point, we still need eyeballs on a physical page. How many times have we seen a funny looking page because of CSS errors? Or worse yet, an important button like say, “Buy now” “missing” because someone changed the CSS and now the button blends in with the background? Logically, the page still works, and even from a traditional test perspective, the button can be clicked, and the DOM (used in UI Test verification) is perfect. Visually, however, the page is broken; this is where visual testing comes into play. Visual testing allows us to use automated UI testing with the power of AI to help us determine if a page “looks right” aside from just “functions right.”

Published in Uncategorized

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.