Skip to content

About

Executable OKW4Robot examples against public demo websites (SauceDemo, ExpandTesting). Install, run, compare.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

OKW Examples

Executable examples for OKW4Robot -- a driver-agnostic keyword architecture for Robot Framework.

Each example uses publicly available demo websites and can be run immediately after installation. No application code, no test infrastructure -- just pip install and robot.

Quick Start

pip install -r requirements.txt

Run SauceDemo Login Tests

cd selenium/saucedemo
robot tests/SauceDemo_Login.robot

Run SauceDemo SetContext Tests

cd selenium/saucedemo
robot tests/SauceDemo_SetContext.robot

Run ExpandTesting Dynamic Table Test

cd selenium/expandtesting
robot tests/DynamicTable.robot

Prerequisites

  • Python 3.10+
  • Chrome browser (for Selenium examples)
  • ChromeDriver matching your Chrome version (for Selenium examples)
  • A reachable Docker host (for env-docker examples)

Examples

Example Website What it demonstrates
SauceDemo Login saucedemo.com Login with valid/invalid/locked users, template-driven tests
SauceDemo SetContext saucedemo.com Repeating GUI structures (product cards) without per-item locators
Dynamic Table expandtesting.com Table access by header names, dynamic content
ENV Docker Basic Docker host (local/remote) Environment provisioning lifecycle with PostgreSQL

Project Structure

okw-examples/
  requirements.txt
  selenium/
    saucedemo/
      locators/            # YAML GUI object definitions
      tests/               # Robot Framework test suites
      README.md
    expandtesting/
      locators/
      tests/
      README.md
  rest-api/
    expandtesting/tests/   # REST API test suites
    dummyjson/tests/
  ssh/
    basic/tests/           # SSH command execution
  env-docker/
    basic/
      components/          # YAML environment definitions
      tests/               # ENV lifecycle tests
      README.md

How OKW Works

OKW separates what to test from how to find GUI elements:

  • Tests use abstract keywords: SetValue, ClickOn, VerifyValue
  • Locators are defined in YAML files -- no hardcoded selectors in test code
  • Drivers (Selenium, FlaUI, RemoteSwing) are loaded automatically via YAML config

This means the same test keywords work across web, desktop, and Java Swing applications. Only the YAML locator files differ.

Links

About

Executable OKW4Robot examples against public demo websites (SauceDemo, ExpandTesting). Install, run, compare.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages