Exit course
Chapter 1 of 10 Beginner 6 min read 1 quick check Updated

Robot Framework Tutorial for Beginners

A free, hands-on Robot Framework tutorial: keyword-driven tests with SeleniumLibrary and the Browser library, resource files, data-driven templates, tags, parallel runs with Pabot, reports and CI, all on a cloud grid.

What you will learn

  1. Robot Framework Tutorial for Beginners
  2. Install Robot Framework in a Python virtual environment
  3. Your first Robot Framework test with SeleniumLibrary
  4. Variables, resource files and user keywords
  5. Run Robot Framework tests on TestingBot
  6. Robot Framework Browser library: Playwright on TestingBot
  7. Data-driven tests with Robot Framework templates
  8. Tags and parallel test runs with Pabot
  9. Robot Framework reports, CI and test status on TestingBot
  10. Knowledge check
On this page
  1. What Robot Framework is
  2. The pieces you will use
  3. When Robot Framework fits, and when it does not
  4. SeleniumLibrary or Browser library?
  5. What you'll build
  6. Prerequisites

Last reviewed November 2026 against Robot Framework 7.5.1, SeleniumLibrary 6.9.0, Browser library 21.0.0, Pabot 5.2.2 and Python 3.13.

This course builds a small browser test suite with Robot Framework, from an empty folder to a suite that runs in parallel on a cloud grid and in CI. Every example was run: first against local Chrome and Firefox, then on the TestingBot grid on Chrome, Edge, Firefox and Safari.

What Robot Framework is#

Robot Framework is an open-source test automation framework written in Python and released under the Apache 2.0 licence. It started at Nokia Networks and is now maintained with the support of the Robot Framework Foundation. It is used for acceptance testing and robotic process automation, and for web testing in particular it is one of the most widely used tools outside the JavaScript world.

Its defining idea is that tests are made of keywords. A keyword is a named step, like Open Browser, Input Text or Title Should Be. Some keywords come from libraries written in Python; others you write yourself by combining existing keywords. A test case is a list of keyword calls with their arguments:

*** Test Cases ***
Submit The Web Form
    Open Browser    https://www.selenium.dev/selenium/web/web-form.html    chrome
    Title Should Be    Web form
    Input Text    id:my-text-id    Robot Framework
    Click Button    css:button[type=submit]
    Wait Until Page Contains    Received!
    [Teardown]    Close Browser

There is no def, no braces and no assert. Cells are separated by two or more spaces (four is the convention), which is why Open Browser is one keyword name and the URL after it is an argument. That single rule explains most beginner syntax errors.

The pieces you will use#

Piece What it is In this course
Robot Framework The runner: parses .robot files, runs keywords, writes the log and report the robot command
BuiltIn Standard library, always loaded: Should Be Equal, Log, Set Variable, Run Keyword If... everywhere
SeleniumLibrary Keywords on top of Selenium WebDriver chapters 2 to 4
Browser library Keywords on top of Playwright chapter 5
Pabot A parallel runner for Robot Framework suites chapter 7
Your own keywords Written in .robot or .resource files, or in Python from chapter 3 on

The same structure covers mobile apps (AppiumLibrary, see the TestingBot Appium guide for Robot Framework) and APIs (RequestsLibrary), which is a large part of the framework's appeal: one syntax and one report format across very different kinds of tests.

When Robot Framework fits, and when it does not#

Robot Framework is a good choice when:

  • People who do not write code need to read or write tests. A well-written suite reads like a specification. Testers, analysts and product owners can review it, and often contribute to it, without learning Python.
  • You test across layers. Web, mobile, API, database and SSH keywords all live in the same suite and produce one report.
  • You want a report out of the box. Every run writes a detailed HTML log, with every keyword, argument, timing and screenshot, without installing anything extra.
  • Your team already knows Python, because anything the libraries lack becomes a small Python keyword library (chapter 4 writes one).

It is a weaker fit when:

  • The team is all developers who prefer code. If everyone is comfortable in pytest or Playwright Test, the keyword layer adds indirection without adding readers. The Selenium with Python and pytest and Playwright courses cover those routes.
  • Tests need complex logic. Robot Framework has IF, FOR and WHILE, but heavy branching in .robot files becomes hard to read. Push that logic into Python keywords and keep the test cases flat.

A new test fails with No keyword with name 'Input Text id:my-text-id' found. What is the most likely cause?

Robot Framework splits cells on two or more spaces. With a single space the locator becomes part of the keyword name, so the framework looks for a keyword that does not exist. A missing library gives a different error: the library import fails first.

SeleniumLibrary or Browser library?#

Both drive real browsers and both run on TestingBot. The course teaches SeleniumLibrary first, because it is the library most existing suites use and its keywords map one to one onto WebDriver, then shows the same tests in the Browser library.

SeleniumLibrary Browser library
Engine Selenium WebDriver Playwright (needs Node.js)
Waiting explicit Wait Until ... keywords built-in auto-waiting on every action
Assertions ... Should ... keywords getters with an assertion operator, Get Text id=message == Received!
Remote grid remote_url= to a WebDriver hub Connect To Browser to a Playwright endpoint

What you'll build#

Chapter You add
1. Install a virtual environment, the libraries, rfbrowser init
2. First test a SeleniumLibrary test, locators, waits, and the log file
3. Variables, resources and keywords readable tests built from your own keywords
4. Run on TestingBot remote browsers, tb:options, build names, pass/fail status
5. Browser library the same tests on Playwright, locally and on TestingBot
6. Data-driven tests test templates for many inputs
7. Tags and Pabot selecting tests and running them in parallel
8. Reports and CI output files, rebot, GitHub Actions
9. Knowledge check ten questions on the decisions the course made

The final project:

robot-course/
  requirements.txt
  libraries/
    TestingBot.py          builds remote browser options
  resources/
    browser.resource       open/close the browser, locally or on the grid
    web_form.resource      keywords for the web form page
    login.resource         keywords for the login page
    playwright.resource    the Browser library version
  tests/
    web_form.robot
    login.robot
    playwright/
      web_form.robot

The tests use two public practice pages: the Selenium project's web form and the login page of The Internet, a site built for exactly this kind of exercise.

Prerequisites#

  • Python 3.11 or newer. The Browser library 21 requires 3.11; Robot Framework itself runs on older versions. The examples ran on Python 3.13.
  • Node.js 22, 24 or 26 for the Browser library in chapter 5 (or its [bb] extra, which bundles Node).
  • Chrome installed locally; Firefox too if you want to follow the cross-browser parts.
  • No Python experience is required for most of the course. Chapter 4 has a 20-line Python file, explained line by line.

The certificate at the end of this course is issued by TestingBot, not by the Robot Framework Foundation: it records that you passed the exam and ran your own suite on the grid.