Testing in the CI pipeline
Your tests are only as good as when they run. CI runs them on every change, minutes after it's made — here's how to make that feedback loop actually work.
7 steps · 5 minWhat CI actually is
Continuous Integration is a robot with one job: every time anyone pushes code, build the app and run the tests — automatically, within minutes. No 'testing phase' at the end. Every change gets checked while it's still small and fresh in someone's head.
Remember the cheapest-bug lesson? CI is that idea built into the team's plumbing.
A developer pushes a change and CI turns red 4 minutes later. Why is this a *good* morning for the team?
Fast feedback first
Pipelines run in stages, cheapest first: lint and unit tests in the first minutes, API tests next, the slow end-to-end suite last. If a unit test fails, the pipeline stops immediately — no point running an hour of UI tests on code that can't add two numbers.
This is the test pyramid again, laid on its side and turned into a schedule.
Your full end-to-end suite takes 50 minutes, so developers only get feedback once an hour. What actually fixes this?
Red means stop
One rule separates teams where CI works from teams where it's wallpaper: a red main build is everyone's top priority. Fix it or revert the change — nothing new ships on top of red. Break the rule for a week and red becomes the normal color of the dashboard.
This is the flaky-tests lesson at team scale: the pipeline only protects a team that believes it.
Main has been red for three days ('a known issue, ignore it') and new changes keep merging on top. What's the real damage?
Where you fit
In a CI world the tester's job moves upstream: you decide what earns a place in the pipeline, keep it fast and trusted, and treat its gaps as your exploration map. The robot runs the checks; you decide what's worth checking.
Last lesson in this pathway: with limited time, how do you decide what to test at all?
Lesson complete.
You now see the pipeline as a feedback machine: every change tested in minutes, fast tests first, and a red main build treated as the team's top priority.