Things to consider when running visual tests in CI/CD pipelines: Container Pipeline Edition (Part 3)
Nov 14, 2020Jessica Deen

Summary
This post, the third in a series, details running visual tests in container-based CI/CD pipelines. It explains the benefits of containerized tasks, the challenges of not having local Chrome, and how to use Docker Compose with Selenium Hub and nodes. It provides specific YAML examples for Codefresh, including defining service containers (Selenium Hub, Chrome node, Firefox node), performing HTTP checks, setting Applitools environment variables, and running visual tests with Maven. It also offers guidance for Jenkins and JFrog Pipelines, and provides a sample project for local Docker Compose experimentation.
More from the Visual Testing in CI/CD Pipelines trail
- 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: Getting Started (Part 1)
- Announcing easy to use browser-based exploratory testing for Visual Studio Team Services
- Using Internet Explorer 11 and not able to record a web performance test successfully?
- Using Microsoft Visual Studio 11 Beta Feedback Client tool with Windows 8 Metro Style applications