CI/CD Pipeline & API Automation

API test automation framework integrated with a Jenkins pipeline and Docker — built to practice the kind of quality engineering that lives inside a real DevOps workflow.

---

What this project does

Automates API regression testing against a practice booking system (Restful Booker) using Playwright and Postman/Newman. Tests run nightly inside a Jenkins pipeline, executed in a Docker container so the environment stays consistent regardless of where the pipeline runs.

The focus wasn't just writing tests — it was wiring them into a pipeline and making them run reliably without manual steps.

---

Results

• Cut manual regression time by 50% through nightly automated runs
• Achieved 98% CRUD coverage across booking API endpoints
• Caught 30+ integration defects before they reached production
• Improved booking system uptime by 25% by catching regressions early

---

Tech stack

• Playwright (JavaScript) — API test suites
• Postman / Newman — collection-based API testing
• Jenkins — CI/CD pipeline, nightly schedule
• Docker — containerized test runner for environment consistency

---

Project structure

tests/              # Playwright API test files
test-data/          # Input data for parameterized test cases
utils/              # Shared request helpers and utilities
playwright.config.js
package.json

---

Run locally

npm install
npx playwright test

To mirror the CI environment:

docker build -t api-test-runner .
docker run api-test-runner

---

Why this matters for DevOps

Writing tests is one part. The other part is making them run automatically, in isolation, on a schedule, without breaking when the environment changes. That is what this project practices — Docker for environment parity, Jenkins for scheduling and visibility, structured test data to keep runs reproducible.

Planned improvements:

• Migrate pipeline from Jenkins to GitHub Actions
• Provision ephemeral test environments with Terraform on AWS
• Push test reports to S3 for trend tracking