Project 04 / QA Automation

Sentinel

A starter framework for running API and UI tests, ready to plug into a CI pipeline.

Role

Solo build — test automation

Stack

Java 17 Maven JUnit 5 Selenium RestAssured Jenkins

FIG. 01 — Architecture Two test layers, one Jenkins pipeline. Reports flow downstream to S3 when configured.

The Idea

Most teams write tests once and then watch them rot — running locally, breaking on someone else's machine, never actually wired into deployment. Sentinel is built to skip that fate.

It's a lightweight, extensible framework that bundles API smoke tests and UI test automation behind one Maven build and one Jenkinsfile. Drop your project's tests in, point Jenkins at the repo, and you have a CI-runnable test suite from day one.

The goal isn't to be a full QA platform out of the box — it's to be the foundation that grows into one as a team adds real tests against a real app.

What's in the box

Four building blocks, ready to extend.

/ 01

API testing RestAssured · JUnit 5

A configured RestAssured + JUnit 5 setup for writing API smoke tests against any HTTP endpoint. The framework handles the boilerplate so each new test stays small.

/ 02

UI automation Selenium · WebDriverManager

Selenium WebDriver wired up with WebDriverManager so browser drivers get resolved automatically — no manual chromedriver paths, no setup pain when running across machines.

/ 03

CI pipeline Jenkinsfile · Pipeline-as-Code

A Jenkinsfile defines the build, test, and report stages declaratively. Same pipeline runs on every commit, so test results stay reproducible across machines and over time.

/ 04

Containerized runs Docker · docker-compose

A Dockerfile and docker-compose setup give you isolated test environments — useful for CI runners that don't have Java or browser drivers installed by default.

NOTE

Sentinel is a starter framework, not a turnkey QA suite. It's the scaffolding — config loader, page-object layout, CI pipeline, Docker setup — ready for real tests to be written against a real product. The point is that the boring parts are already solved.

Want to poke around the code?

View on GitHub ← Back to projects