Modern software isn’t finished when it compiles - it’s finished when it ships, tested, to real users. CI/CD (Continuous Integration / Continuous Deployment) automates that journey, and Selenium supplies the crucial final check: driving a real browser through your application exactly as a user would.
Together they answer the question every team fears: did that last change quietly break something? - within minutes of the change being made.
How I use it
Automated browser testing
Writing Selenium scripts that click, type, and assert their way through an application - turning a manual test plan into a suite that runs identically every time.
Pipeline construction
Building pipelines with Git-based workflows that trigger on every commit: build, test, and deploy stages that give a team continuous confidence in its main branch.
Test strategy
Where UI tests fit alongside unit and integration tests - the testing pyramid, what each layer catches, and why slow, brittle UI suites are a design smell rather than a necessity.
DevOps culture
The bigger idea the tools serve: small changes, fast feedback, shared responsibility for quality - the working practices behind every high-performing software team.
Explore: a CI/CD pipeline with automated testing
Follow one code change from a developer’s commit to production. Click or tap each stage to explore it.
In the classroom
Students build a pipeline for their own project and then experience the payoff: they commit a change, watch the stages run, and see a Selenium test catch a bug before any user could. That moment converts more students to automated testing than any lecture.
We treat a red pipeline as the system working, not as failure - the entire point is that problems surface in minutes, in private, instead of in production.
Test yourself
Three quick questions - click an answer to check it instantly.
1. What does Selenium automate?
2. What does CI stand for?
3. What should happen when a test fails in a CI/CD pipeline?
Where this leads
Pipeline and test-automation skills appear in nearly every developer and DevOps job description, and they’re often what distinguishes a junior who ships confidently from one who hopes. This skill is the engineering heart of my Agile & IT Management teaching, where students build and run these pipelines on their own team projects.
