Automated testing has become a core practice in modern software development.


Today, testing doesn’t just happen on a local machine—it is integrated directly into Continuous Integration (CI/CD) pipelines, ensuring every code change is validated before reaching production.

In this article, we explore and compare three widely used testing management tools within CI/CD environments: GitHub Actions, GitLab CI/CD, and Jenkins.


Each one includes a real-world pipeline example so you can understand how test automation works in practice.

💡 Why Testing in CI/CD Matters

Automated test executions help teams:

• Prevent bugs before merging code
  


• Detect regressions quickly
  


• Standardize test execution across environments
  


• Improve software reliability and delivery speed
  


• Reduce manual testing overhead
  

Today’s development workflows expect speed and consistency—CI/CD testing delivers both.

🧩 Tools Overview

🟦 GitHub Actions

A cloud-based automation platform built into GitHub.


It uses YAML workflows and triggers on events like push, merge, or pull_request.

🟥 GitLab CI/CD

A complete DevOps platform where CI/CD is deeply integrated.


It uses “runners” to execute jobs and supports built-in testing, security scans, and deployment pipelines.

🟩 Jenkins

An open-source automation server used for customizable pipelines.


Requires installation and configuration but offers massive flexibility.

🌍 Example Scenario

To compare the tools fairly, we use the same simple case:

👉 Run test scripts automatically after every push.

We assume the project uses a test command such as:

npm test -- --coverage

🔧 Real CI/CD Pipelines

🟦 1. GitHub Actions Pipeline

Create a file:

.github/workflows/ci.yml

Add:

name: Run Automated Tests



on:

  push:

    branches: [ "main" ]



jobs:

  test:

    runs-on: ubuntu-latest



    steps:

      - name: Checkout repo

        uses: actions/checkout@v3



      - name: Install packages

        run: npm install



      - name: Run unit tests

        run: npm test -- --coverage



      - name: Upload coverage results

        uses: actions/upload-artifact@v4

        with:

          name: coverage

          path: coverage/

🟥 2. GitLab CI/CD Pipeline

Create:

.gitlab-ci.yml

Add:

stages:

  - test



unit_tests:

  stage: test

  script:

    - npm install

    - npm test -- --coverage

  artifacts:

    paths:

      - coverage/

🟩 3. Jenkins Pipeline (Jenkinsfile)

Create:

Jenkinsfile

Add:

pipeline {

    agent any



    stages {



        stage('Install') {

            steps {

                sh 'npm install'

            }

        }



        stage('Run Tests') {

            steps {

                sh 'npm test -- --coverage'

            }

        }



        stage('Archive Coverage') {

            steps {

                archiveArtifacts artifacts: 'coverage/**'

            }

        }

    }

}

📊 Quick Comparison

📁 Public Example Repository

Example structure:

/src

/tests

.github/workflows/ci.yml

.gitlab-ci.yml

Jenkinsfile

README.md

You can publish it as:

https://github.com/dennisdhm7/ci-testing-demo

🧩 Key Takeaways

• 
  GitHub Actions is the easiest for cloud-native projects.
  


• 
  GitLab CI/CD provides an all-in-one DevOps solution.
  


• 
  Jenkins offers powerful customization for enterprise environments.
  


• All three support automated testing inside CI/CD pipelines.

Automating tests ensures consistent, reliable, and high-quality software delivery.

✍️ Author

Christian Dennis Hinojosa Mucho


Software Engineering Student — UPT