Automation testing is a cornerstone of modern software development, enabling teams to deliver high-quality applications faster. However, as automation test suites grow in size and complexity, their execution time can become a bottleneck, delaying feedback and increasing costs. To address these challenges, teams are turning to innovative solutions like Docker and Cucumber to streamline their testing processes.

In this article, we’ll explore how Docker and Cucumber work together to enable parallel execution, reduce costs, and improve the reliability of automation testing. We’ll also discuss how ZippyOPS, a trusted microservice consulting provider, can help you optimize your DevOps, DevSecOps, and Cloud operations.

Why Cucumber for Automation Testing?

Cucumber stands out among automation frameworks for its ability to write tests in a human-readable, business-oriented language. By using Gherkin syntax, Cucumber allows teams to define test scenarios in plain English, making them accessible to both technical and non-technical stakeholders. This approach not only improves collaboration but also ensures that tests are easy to understand and maintain.

Combining Docker and Cucumber for Efficient Testing

Docker, a leading containerization technology, provides an isolated and consistent environment for running applications. When combined with Cucumber, Docker enhances the reliability and scalability of automation testing. Here’s how:

1. Parallel Execution: Docker enables parallel execution of test containers, significantly reducing the total execution time of automation suites.

2. Consistency and Reliability: By running tests in isolated environments, Docker eliminates inconsistencies and flaky test executions.

3. Scalability: Docker’s lightweight containers allow teams to scale their test infrastructure efficiently, accommodating larger test suites without significant cost increases.

4. Ease of Maintenance: Docker and Cucumber simplify the long-term maintenance of automation suites, enabling seamless updates to dependencies and test scenarios.

Architecture of a Docker and Cucumber-Based Automation Framework

To build an efficient automation testing framework, we’ll use the WebdriverIO (WDIO) framework as the base, combined with Docker for containerization. Here’s an overview of the architecture:

1. Docker Selenium Grid Architecture

The Selenium Grid architecture can be easily set up using Docker images provided by Selenium. This includes:

• Selenium Grid Hub: Acts as the central point for distributing test requests.

• Browser Nodes: Containers running browser instances to execute tests.

2. Docker Image of the Automation Suite

To containerize the automation suite, we create a Docker image using a Dockerfile. This image includes the automation code, dependencies, and a base Node.js image for lightweight execution.

Here’s a sample Dockerfile for the automation suite:

FROM node:20-alpine

## Install Python 3 and update PATH

RUN apk add --no-cache python3

## Set the Python 3 binary as the default python binary

RUN ln -s /usr/bin/python3 /usr/local/bin/python

## Add Python 3 binary location to the PATH environment variable

ENV PATH="/usr/local/bin:${PATH}"

## Install build tools

RUN apk add --no-cache make g++

WORKDIR /cucumber-salad
ADD . /cucumber-salad

## Install all the required libraries using npm install

RUN apk add openjdk8 curl jq && npm install

## Use the Feature Name as Environment Variable

ENV FEATURE=/.feature
ENV ENVIRONMENT=staging
ENV TAG=@Regression
ENV CHROME_VERSION=109.0.5414.74
ENV HOST=***.***.**.***

3. Docker Compose File

The docker-compose file orchestrates the Selenium Grid architecture and automates the execution of multiple test containers. Here’s a sample docker-compose file:

version: "3"
services:
hub1:
image: seleniarm/hub:latest
ports:
- "4442:4442"
- "4443:4443"
- "5554:4444"

chrome1:
image: seleniarm/node-chromium:latest
shm_size: '1gb'
depends_on:
- hub1
environment:
- SE_EVENT_BUS_HOST=hub1
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- HUB_HOST=hub1
- SE_NODE_MAX_SESSIONS=2
- VNC_NO_PASSWORD=1*

To start the Selenium Grid and run multiple browser nodes, use the following command:

docker-compose up -d --scale chrome1=2 --scale chrome2=2 hub1 chrome1 hub2 chrome2

This command scales the browser nodes, enabling parallel execution of the automation suite.

Benefits of Using Docker and Cucumber

• Reduced Execution Time: Parallel execution of test containers significantly cuts down the total testing time.

• Cost Efficiency: Docker’s lightweight containers reduce infrastructure costs compared to traditional virtual machines.

• Improved Reliability: Isolated environments ensure consistent and reliable test executions.

• Scalability: Docker allows teams to scale their test infrastructure effortlessly, accommodating larger test suites.

• Ease of Maintenance: Docker and Cucumber simplify updates and maintenance of automation suites.

Conclusion

By combining Docker and Cucumber, teams can revolutionize their automation testing processes, achieving faster execution times, reduced costs, and improved reliability. This approach not only enhances the efficiency of testing but also ensures that teams can deliver high-quality applications with confidence.

At ZippyOPS, we specialize in consulting, implementation, and management services for DevOps, DevSecOps, DataOps, Cloud, Automated Ops, AI Ops, ML Ops, Microservices, Infrastructure, and Security. If you’re looking to optimize your automation testing workflows or need expert guidance, explore our services, check out our products, or view our solutions. For a demo, visit our YouTube playlist.

If this seems interesting, please email us at [email protected] for a call. Let’s build scalable, efficient, and secure systems together!