Browser Library 21 added a feature that surprises people who have written web tests by hand for years: you can click through a page and have the library write a Robot Framework keyword for you, live, while the browser is open.
What the recorder does
Browser Library is the modern web-automation library for Robot Framework, built on Playwright. Version 21 adds two keywords, Record Keyword and Record Keywords. You drop one into a test, run it with a visible browser, and a small recorder toolbar appears on the page. From there, every click and every field you fill is captured as a Robot Framework keyword call. Stop the recorder, and the steps are written into your suite as a reusable user keyword.
Here is all it takes to start:
*** Settings ***
Library Browser
*** Test Cases ***
Capture A Login
New Browser chromium headless=False
New Page https://practicesoftwaretesting.com
Record Keyword Log In As A Customer
Run that, log in by hand, close the recorder, and you have a Log In As A Customer keyword you did not type.
The part the demos skip
A recording is a starting point. It captures your actions, the clicks and the fills, but not the checks that make it a test, so nothing is verified yet. And a flat list of recorded steps still needs shaping into a well-named, reusable keyword.
The value of the recorder is real: it saves typing and writes the action steps for you. The quality still comes from you: naming steps for intent, splitting a long recording into keywords that read well, and adding the checks that turn a click-through into a real test. That is the difference between a recording and a maintainable suite, and it is exactly the craft the certification is about.
Frequently asked questions
Which version do I need?
Record keywords arrived in Browser Library 21.0.0 (November 2026). It needs Robot Framework 7.1.1 or newer. The robotframework-browser[bb] package bundles its own Node.js, so there is nothing extra to install.
Does the recorder work headless?
No. The recorder needs a browser you can see, so run with headless=False.
Can I record straight into a resource file?
Yes. Pass a target file as a second argument, and use Record Keywords to capture several in one session.
Should I ship recorded tests as they come out? No. Treat a recording as a first draft: name it for intent, add the assertions, and review it before it joins your suite.
Recording gets you a first keyword in seconds. Turning that into a readable, stable suite you would hand to a team is the skill that earns the certification. The Robot Framework Certified Professional course takes you from your first keyword to a suite you trust, with web UI and API testing covered end to end.