The part of automation that runs without you
A suite that only runs on your laptop is a hobby. This is the route from a test you can run by hand to one that runs on every commit, reports itself, and tells the team what broke – which is what a 2–5 year automation role is actually asking for.
Have something worth running
A pipeline is only as useful as the suite inside it. Build the suite first.
A framework, then a pipeline
Start from a working project rather than an empty repository. The Download Center has the Playwright, Selenium Java, Selenium Python, API and mobile frameworks as ZIPs, each with the structure a pipeline expects: a runner, a config, a report folder and no hard-coded machine paths.
Make it run on a machine that is not yours
CI/CD and DevOps for testers
Jenkins and GitHub Actions, what belongs in a pipeline and what does not, parallel runs, artefacts and reports, and the environment problems that only appear on a build agent.
Containers and the grid
Docker for a repeatable test environment and Selenium Grid for running wide instead of long. The Download Center carries a docker-compose for a grid and a Jenkinsfile and GitHub Actions workflow you can read before you write your own.
Be able to talk about it
Nobody is asked to write a Jenkinsfile in an interview. They are asked what happens when the pipeline goes red at 2am.
- Where tests belong in a pipeline, and which ones never do
- How a flaky test is handled without disabling it
- Artefacts, reports and what a developer actually reads
- Running in parallel without tests fighting each other
- Secrets, environments and test data on a shared agent
Questions and practice
The interview bank has the DevOps and CI/CD rounds, and the training programme covers it end to end if you would rather be taught it than read it.