Robot Framework — UI Testing
Practical notes for structuring UI automation with Robot Framework: page-level .resource files, locator hygiene, and stable waiting. Use this section together with your stack’s official docs (SeleniumLibrary, Browser library).
Topics in this section
| Topic | What you will learn |
|---|---|
| Page Object Pattern & Locators | Model pages as .resource files with variables + keywords; locator priority; SeleniumLibrary vs Browser (Playwright). |
| Wait Strategies & Flakiness Control | Replace fixed sleeps with explicit waits and retries; reduce flakiness; pyramid-friendly UI scope. |
| UI Testing — Step by Step | SeleniumLibrary basic → keywords → data-driven → Browser (Playwright). Progressive examples. |
| Practical — Full UI Framework | Complete project: Browser (Playwright), page objects, DataFactory, E2E flow. |
Quick orientation
- Tests (
*.robot) should read like scenarios: import page resources and call business-level keywords (Login With Valid User), not raw clicks on every line. - Pages are resource files, not Python classes: one file per screen or coherent fragment, with a
*** Variables ***block for selectors and*** Keywords ***for actions.