How this course works
This course is hands-on: you learn Robot Framework by doing it in your own editor. Each lesson mixes short reading with tasks you carry out in VS Code. This first chapter is a quick tour of the pieces you’ll meet. There is nothing to install yet.
Reading, and the three callouts
Section titled “Reading, and the three callouts”Most of a lesson is plain reading like this. Watch for three highlighted notes:
Tasks and “Done when”
Section titled “Tasks and “Done when””A lesson is a short list of tasks. Each task heading carries a badge for its kind: edit (write or change a file), run (run a command), or read. A task ends with a Done when line that states what to verify in your workspace, usually that a suite passes or a file exists. When it holds, tick Done on the task; the tick is how this site tracks your progress.
Writing code — worked example and hints
Section titled “Writing code — worked example and hints”Later, some tasks ask you to write something — a suite, a keyword, a variable. These show a goal (what to build, not the code) and a runnable worked example over different data to adapt rather than copy. If you get stuck, a hint ladder reveals help one rung at a time, and its final rung is the full solution — so you always have a way forward. Your first real build-task arrives in the next chapter.
Running commands
Section titled “Running commands”A command appears in a code block with a Copy button. Paste it into a terminal in VS Code (Terminal → New Terminal) opened in your lab folder:
echo "Ready for Robot Framework."Some lessons also show a command running, as a short replay you can watch and re-play:
Quizzes
Section titled “Quizzes”A short quiz closes every lesson — like the one below. Pick an answer and the explanation shows the reasoning either way. Your first answer stays in this browser, and quizzes never block your progress.
Your progress
Section titled “Your progress”The sidebar lists every part, chapter, and lesson; Previous and Next at the bottom of each page follow the course order. Each part’s overview page shows which lessons you have finished, and every lesson’s key terms collect in the Glossary.
Ticks, quiz answers, and your runner choice are stored in this browser only. Another browser or cleared site data starts fresh, and the course overview can reset them.
That’s the whole format. Answer the quick check below, then continue with the setup lesson.
Take the tour of how this course works
Check your understanding
Quick recall. Your first answer stays in this browser; the quiz never blocks your progress.
A task's “Done when” line holds in your workspace. What next?
“Done when” states what to verify; you check it yourself and tick Done. The tick is stored in this browser and shows on the part overview.
Show the answer
Answer: Tick Done on the task — it records your progress in this browser — “Done when” states what to verify; you check it yourself and tick Done. The tick is stored in this browser and shows on the part overview.
How do quizzes work here?
Quizzes are for you: your first answer is remembered in this browser and the explanation shows the reasoning either way, but they never gate the lesson.
Show the answer
Answer: They give immediate feedback and never block your progress — Quizzes are for you: your first answer is remembered in this browser and the explanation shows the reasoning either way, but they never gate the lesson.
Key terms
- Done whenconcept
- The line that ends each task: what to verify in your workspace before you tick the task done.
- hint ladderconcept
- Staged hints on a build-task, revealed one at a time, with the full solution as the final rung — help is always available and you are never stuck.
- Glossaryconcept
- Every key term from the course in one place, filterable by kind, each linking to the lesson that introduces it.