delvun✕ FAIL
this page is a check run · 0 / 7 pass · each section is a check and passes when you reach it · the last one is yours✕ FAIL · 0 / 7 · nothing verified yet
Prove you can.
✕ FAILThis page is a check run. It turns green as you read.
For QA engineers who want the infrastructure side of the SDET job. Every lesson is a broken environment that opens in your browser. You fix it. A checker inspects the real state — containers, ports, exit codes — never a typed answer. Red until it's genuinely fixed.
· nothing_to_install · not runnothing to download · 5 free scenarios · 60-minute sessions
sandbox · ready28:14 left
learner@sandbox:~/payments-api$ make ci 2>&1 | tail -4FAILED tests/test_payment_confirms.py::test_payment_confirms_after_block - re...9 failed, 5 passed in 1.22smake: *** [Makefile:8: ci] Error 1
checks · 2 / 5Run checks
✓image_buildspass
✓tests_not_removedpass
✕tests_green_in_containerfail
✕service_reachable_by_namefail
API_URL=(not set in the test container) $ getent hosts api 172.18.0.3 api $ curl -s $API_URL/health → 000
Inside CI, localhost is the test container itself — not the service.
✕no_time_dependent_assertionsfail
· outcome_is_concrete · not run
after step 1 · in plain words
What you can do at work on Monday.
Not a certificate. Four things you will be able to do, each one verified by a checker — not by you, and not by us.
Read a red CI run and name which layer broke — code, container, network or time — before you ask anyone.
Put your test suite in a container and run it the same way on your laptop and in the pipeline.
Stand up a disposable environment for every pull request — and tear it down.
Tell a flaky test from a broken one, and fix the cause instead of adding a retry.
· sandbox_opens_in_browser · not run
1 · open
One click. A broken environment starts in your browser.
Real terminal, real containers, disposable. Ports and service names differ per learner.
2 · fix
You work in the sandbox until it does what the brief says.
No multiple choice. No "type the command". Just the machine.
3 · check
A checker on the server inspects the real state of the world.
Containers, ports, HTTP responses, exit codes, database rows. Red until it's genuinely fixed.
· route_has_a_next_step · not run
Step 1
QA → SDET: the infrastructure your tests run on
6 scenarios · 3 gates
3 free
→
Next
A partner course
DevOps, taught by someone
who does it full time
· price_is_one_time · not run
Free
$0
- 5 scenarios per account
- 60-minute sessions, reset any time
- Full check panel, no gates
Step 1 · one-time purchase
no subscription
$149 · $59 in India
- All Step 1 scenarios and gates
- Unlimited sessions, 2-hour time-box
- Updates when a scenario moves to a new version
Step 1 is not on sale yet. No waiting list games: one email, once.
· author_is_real · not run
"I moved from QA automation into DevOps. Every scenario here is something that actually broke on me — and the checker doesn't care who wrote it."
— Alex, QA automation engineer who moved into DevOps
◌ you_open_a_scenario · running
The last check is yours.
Sign in with a magic link — email only, no passwords. The first scenario opens in about 30 seconds.