“DevOps for QA” is a hands-on course that closes the key gap in a tester’s knowledge after learning APIs. You will not just check requests — you will understand how those requests travel through real infrastructure, from commit to production.
What you will learn
Your own environment
You will set up a working Linux environment (WSL2 or macOS) that behaves the same for everyone — Docker, Git, CLI.
Docker without waiting
You will bring up the stand with docker compose yourself and diagnose it: ps → logs → exec, rebuild, resetting state.
Tests in the pipeline
You will read .gitlab-ci.yml, add Newman as a job with reports and set up a quality gate that blocks the merge request.
Kubernetes for QA
You will understand why a pod is in CrashLoopBackOff or not Ready, and how to check a release in the cluster with kubectl and Rancher.
Release verification
You will verify a release after deploy: healthcheck.sh, a verify stage in CI, Grafana dashboards and logs in Loki.
Speaking DevOps
You will know what else DevOps does and where QA fits in — and speak the same language as your team.
After the course you will be able to
- bring up a test environment in Docker on your own;
- read someone else’s pipeline and explain what runs, when and why;
- add Postman/Newman tests to CI with a report and set up a quality gate;
- make sense of pods in Kubernetes: why it crashed, why it is not Ready, which version got deployed;
- write smoke.sh and healthcheck.sh scripts that CI actually reads;
- verify a release after deploy through dashboards and logs (Grafana + Loki);
- speak the same language as DevOps.
Why it is the perfect complement to CSA&API
CSA&API teaches you to test an API; DevOps for QA shows you where the API you test actually lives.
It is the follow-up to our flagship course that takes your skills to the level of systems thinking. You will work effectively with developers, DevOps engineers and automation engineers, understanding the whole cycle from request to production.
About the CSA&API course →How we teach at QARMA
Built for QA
The course was created by Lead DevSecOps engineer Oleh Kurza, together with QA lead Inna Osinna, specifically around testers’ tasks.
Interview skills
Docker, CI/CD, Kubernetes, monitoring — exactly what technical interviews ask about more and more often.
Practice straight away
A practice-oriented format: every skill can go straight into your work on a real project.
Recorded, no deadlines
Watch the sessions whenever it suits you, with no group deadlines. Access from the start date and for life, updates included.
Live support
The teacher is always in touch in the course Telegram chat. A review from Oleh — on request.
Homework with instructions
Homework needs no grading: you get exact step-by-step instructions. If something does not work — ask in the chat.
Course programme
5 sessions · theory + demo + hands-on + homework
What goes on your CV after the course
- Docker
- docker compose
- GitLab CI
- Postman
- Newman
- Kubernetes
- Rancher
- Helm
- Prometheus
- Grafana
- Loki
- WSL2
- bash
- curl / jq
We practise on the course’s own training repository, x-ops-qarma: a Tasks API plus a Demo Shop that breaks itself.
Session 1. Introduction and environment setupwhat DevOps is · WSL2 · Docker · Git · CLI
- the Wall of Confusion between Dev and Ops, DevOps as culture + practices, CALMS
- one environment for everyone: WSL2 + Ubuntu (Windows) or Homebrew (macOS)
- Docker, Git + SSH,
curl/jq/grep/tail, VS Code
A working Linux environment that behaves the same for every student.
Session 2. Docker for QAcontainers · Dockerfile · compose · diagnostics
- container vs VM, images, layers and cache, networks, volumes
- the Tasks API stand: first by hand with
docker run, then with a singledocker compose - diagnostics with
ps→logs→exec, rebuilding after code/env changes, resetting state - checking the API with a Postman collection and Newman in a container
You bring up the stand yourself and no longer wait for someone to “give you an environment”.
Session 3. DevOps and CI/CD for testerspipeline anatomy · Newman in CI · quality gates
- how to read
.gitlab-ci.yml: stages, jobs, image, script, artifacts, rules, variables - the exit code as a contract,
smoke.shinstead of inline scripts - Newman as a job: JUnit + HTML reports in artifacts
- a quality gate: a failed test blocks the merge request; the trap of a “green” pipeline with failed tests
You add tests to the pipeline and set up the gate on your own.
Session 4. Orchestration: Kubernetes and RancherEKS · kubectl · probes · rolling update · Helm · Rancher
- why QA needs Kubernetes: half of “flaky” bugs are orchestration
- Pod, Deployment, Service, Ingress, Namespace, ConfigMap; Running ≠ Ready
- the kubectl minimum for QA:
get→describe→logs --previous,port-forwardfor Postman - rolling update and rollback, the Rancher UI, Helm charts
- a mentor demo on EKS, practice on a local cluster
You understand why a pod is in CrashLoopBackOff and how to check a release in the cluster.
Session 5. QA + DevOps: what next?release verify · synthetic · Grafana + Loki · DevOps competency map
- “The deploy went through — how do you know everything is fine?”: four levels of service health
- observability: golden signals, Prometheus + Grafana + Loki, a Demo Shop that breaks itself
healthcheck.shand a verify stage in GitLab CI: catching “we deployed the wrong version”- the DevOps competency map: what else DevOps does and where QA fits in
You verify a release after deploy and speak the same language as DevOps.
Oleh Kurza
Lead DevSecOps Engineer @ NDA Fortune 500
“I managed to change my own life for the better in a very short time. I documented that path — and I invite those who really want it to follow it.”
- 10 years in IT, 7 of them in DevOps
- from support engineer to senior DevOps in 3 years
- 4 years of mentoring
- ex SoftServe Academy; ex SoftServe, EPAM, Ciklum, Intellias, Avenga
- certifications: AWS Solutions Architect Professional, AWS DevOps Engineer Professional, CKA, HashiCorp Terraform Associate, AWS SysOps / Solutions Architect / Developer Associate, AWS Cloud Practitioner
- author of the DevOps 101 programme for career switchers and beginners
Fun fact: a lawyer by training, who also found time to study dentistry.
LinkedIn →
The course was created together with Inna Osinna, QA Team Lead and founder of QARMA.
Price
DevOps for QA
How a tester becomes more technical without changing careers
The promotional price is valid until 20 October 2026
- 5 recorded sessions (access from 27 October 2026)
- practical homework with detailed instructions
- teacher support in the Telegram chat
- a review from Oleh on request
- lifetime access + course updates
How to pay
Full payment
Full payment goes through the payment system. There you can also split it into up to 6 instalments (the fee is on our side). If needed, you can pay to a crypto wallet — mention it in the form on the site or message @innaosinna on Telegram.
Flexible instalments
Available on request if the payment system does not offer the option you need. Just leave your request in the comment field of the form or message @innaosinna on Telegram.
Company payment
If your company covers your training, we will prepare all the documents and invoices needed so everything goes smoothly ;)
Frequently asked questions
Who is this course for?
For QA of any level who want to move from “I test” to “I understand how the system works”. Especially for CSA&API graduates who want to understand where the API they test lives.
When does it start?
On 27 October 2026. The course is recorded: from the start date you go through the sessions at your own pace.
Are there deadlines?
No, there are no group deadlines.
Who checks the homework?
Homework needs no grading: each assignment comes with exact instructions. If you have questions or get stuck, the teacher is always in touch in the course Telegram group. You can also ask Oleh for a review.
What project will we practise on?
On the course’s own training repository, x-ops-qarma: a Tasks API plus a Demo Shop. We bring it up in Docker, run it through GitLab CI, deploy it to Kubernetes and look at it in Grafana + Loki.
Which OS do I need?
Windows 10/11 (via WSL2) or macOS. We set everything up together in the first session.
Do I have to pay for the cloud or Kubernetes?
No. Practice runs on a local cluster (Docker Desktop / minikube); EKS appears only in the mentor’s demo.
Do I need to know how to code?
No. We write the bash scripts together from scratch.
Do I need to take CSA&API first?
No, it is not required. The course is a logical follow-up to CSA&API, but it can be taken on its own.
How long will I have access to the materials?
For life, course updates included.
How much does the course cost?
$150. For pre-sale participants — $120.
Can I pay in instalments?
Yes. The payment system offers many instalment options: you can choose any convenient bank and number of months. You are not charged a fee for instalments.
Can I get an invoice so my company covers the course?
Yes. Leave a request through the form below with details of what is needed for reimbursement — we will prepare everything and get in touch on Telegram.
Can I pay in crypto?
Yes. Mention it in the form on the site or message @innaosinna on Telegram.
Enrol on the course
Leave your contacts — our manager will get in touch, answer your questions and help with payment.