A template for modern Robot Framework Python libraries.

• Devcontainer for fully reproducible local and remote development
• vscode as IDE
• GitHub
  • Dependabot for automated dependency updates (devcontainer, github-actions)
• Python Tooling
  • uv for dependency management
  • pyproject.toml for centralized tool configuration
  • ruff for linting, formatting and import sorting
  • deptry for finding unused, missing and transitive dependencies
  • vulture for finding dead code
  • pre-commit for preventing commiting bad quality code
• Tests
  • pytest unit tests
  • robot acceptance tests
  • tox-uv for compatibility testing with multiple versions of Python which are not end-of-life

Robot Framework provides three APIs for implementing libraries:

• Static API (and following docs sections)
• Dynamic Library API
• Hybrid Library API

Python libraries may be hosted on different processes or machines than Robot Framework itself is running on. Those libraries are called "remote libraries" and make use of the Remote Library Interface. The PythonRemoteServer implements a generic remote server in Python.

This template provides the easiest possible starting point w.r.t. library design (Static API).

In case you use poetry, pipenv, pip-tools or pip you can use migrate-to-uv to easily migrate to uv.

• https://forum.robotframework.org > Official RF Library template(s)?

This project is partially based on the

• fpgmaas/cookiecutter-uv and
• d-biehl/robot_uv_libtest

repository.