RIDE: a wxPython desktop editor for Robot Framework test data

Why an IDE exists for what looks like plain text

RIDE is described as an IDE exclusive for Robot Framework tests or tasks automation framework, and the package description is Test Data Editor. The word data in that is the whole reason the project exists. A Robot Framework suite is not a program in a conventional language, it is a set of data files with a keyword-driven structure, and editing it in a general purpose text editor leaves the author without the structure of the framework. So RIDE presents the suite as what it is, a set of test cases, keywords and resources, and gives the author a data model view of it. The long description puts the framing plainly, that Robot Framework is a generic test automation framework for acceptance level testing and RIDE is a lightweight and intuitive editor for Robot Framework test data. The homepage is robotframework.org, the licence is Apache-2.0, and the primary language is Python.

The version table, which is a useful map of the project's history

The README has a short list of what the last release supporting each old Python was, and it tells you more about the project than it first appears. Version 2.2 was the last release supporting Python 3.8. Version 2.0.8.1 was the last supporting Python 3.6 and 3.7. Version 1.7.4.2 was the last supporting Python 2.7. The current development version is based on 2.2.4 and supports Python from 3.9 up to 3.14 as of the ninth of July 2026. So the project has dropped Python 2, then 3.6 and 3.7, then 3.8, one at a time, and the branch names in the repository correspond to those boundaries, with release/2.2, release/2.0.8.1 and release/1.7.4.2 all present. For an adopter, the practical consequence is that a project pinned to an old Python can still find the RIDE that supported it, which is unusual for a desktop tool.

Installing: PyPI for the release, a zip archive for the development build

The installation instructions cover two cases, and the distinction matters because the development version is not on PyPI. For the current released version, 2.2.4, on Python 3.9 through 3.14, the command is pip install -U robotframework-ride. For the current development version, 2.2.5dev1, the command installs straight from the repository archive with pip install -U and the URL of the develop.zip file. The release candidate route, 2.2rc1, uses pip install -U with the pre flag, though that instruction is commented out in the README. The README also points at the releases page and at the release/2.2.4 branch for the source of the latest released version, and at the release notes for 2.2.4. So the two supported channels are a stable package and a rolling development build, and the second is a single URL rather than a version number.

pip install -U robotframework-ride

pip install -U https://github.com/robotframework/RIDE/archive/develop.zip

wxPython is the dependency that decides whether it runs at all

The README is unusually precise about wxPython, and this is the single biggest practical constraint on the project. The current version of wxPython is 4.2.5, but RIDE is known to work with 4.0.7, 4.1.1, 4.2.2, 4.2.3, 4.2.4 and 4.2.5. There is also an experimental workflow on Fedora Linux 42 with wxPython 4.2.4 and Python 3.14. wxPython appears in the requirements twice over, in the pyproject dependencies and in the requirements.txt, alongside Pygments for syntax highlighting in the text editor, robotframework itself, PyPubSub, psutil, packaging and chardet, and Pywin32 for Windows only so that a shortcut is created on install. The requests dependency is pinned by Python version, 2.32.5 below Python 3.10 and 2.33.0 from 3.10 up. The older setup.py lists the same requirements, so the project has both a modern Hatchling build and a setuptools path.

Localisation, and the fact that the format itself is localised

There is a detail in the README that points at something bigger than a translated interface. Robot Framework supports, since version 6.1, files with localized definitions, RIDE was updated to accept those files, and the project is working on a localization project to have its GUI in the same languages supported by Robot Framework. You can help in that localization project through Crowdin, and the repository carries a crowdin.yml to go with it. So the GUI and the file format are being localised together, which is unusual and sensible, since a framework whose keywords and test names are localised in the files needs an editor that can display and write that same localisation. The rest of the localisation infrastructure is in the source tree, with the setup.py walking src/robotide/localization to collect the message files and the package data listing the per-module resources under robotide.

The repository layout, and what the build tooling tells you

The top level of the repository is a long-lived Python project with the usual accretions. There is a src/ directory holding the application, a utest/ directory for the unit tests and an rtest/ directory for the Robot Framework tests of RIDE itself, which is the interesting part, since an IDE for a framework can test itself with that framework. There is a doc/ directory, a tools/ directory, a tasks.py for the invoke tasks, a rfgen.py script, an action.yml for the GitHub Action, and a test_all.sh. The configuration files are numerous and informative, with a pyproject.toml, a setup.cfg, a setup.py, a pytest.ini, a tox.ini, a requirements.txt, a requirements-dev.txt, an uv.lock, a .pylintrc, a .coveragerc, a sonar-project.properties, a .travis.yml, an .appveyor.yml and a BUILD.rest file which the README points to for development information. The README.adoc, README.rest and README.md in the same directory suggest a documentation pipeline where the README is generated into several formats.

Testing, support channels and where the project stands

The unit test statuses are shown for Linux on Fedora 42 with Python 3.14 and Ubuntu 22.04 with Python 3.10, for Windows on Python 3.11, and a SonarCloud quality gate, and the README states that the unit tests are currently run on Python 3.10, 3.11 and 3.14. The support surface is wide and worth listing because it tells you where a real user would ask questions. There is a ride channel in the Robot Framework Slack workspace, a RIDE section in the Robot Framework forum under Tools, a robotframework-ide tag on StackOverflow, a Robot Framework users mailing list, the project wiki for usage instructions and tips, the issue tracker, and a Crowdin project for the translations. The releases are v2.2.2 on 2026-01-08, v2.2.3 on 2026-06-10 and v2.2.4 on 2026-07-09, the last push to the repository was on 2026-08-28, and the repository is not archived.

Editorial conclusion

RIDE suits a team that writes Robot Framework suites and wants an editor that understands the format, with resource keyword navigation and a data model view rather than a generic text editor. It is the wrong choice if your tests are written in a general purpose language, because the value here is entirely in the Robot Framework specific understanding, and a poor fit on a headless or containerised setup, since a desktop GUI means a human at a keyboard. Before adopting it, install from PyPI with pip install -U robotframework-ride and read the FAQ in the wiki, and check the wxPython version, because the project lists exactly which wxPython releases RIDE is known to work with and the current one is 4.2.5.

Frequently asked questions

Official sources

1. Issues
2. License: Apache-2.0
3. README
4. Releases
5. robotframework/RIDE on GitHub