Tutorials

Beginners in Robot Framework know the feeling: you sit in front of the first empty .robot file and wonder: How do I start? Which files do I need? How do robot.yaml, conda.yaml, and robot.toml work together?

At this point, it’s easy to lose track – the right starting point is missing, as well as a basic orientation.

For this purpose, I created the Robotmk Starter Repo: a curated set of ready-to-use, CI-tested examples and templates.

In this blog post, I will introduce the three most important examples, explain the underlying concepts, and show how to try them out immediately – either locally or directly in the browser with GitHub Codespaces.

If you’re doing synthetic monitoring with Robotmk in the Checkmk environment, sooner or later you’ll encounter this one question: how do I prevent passwords from ever appearing in plain text?

This article describes how to use the CryptoLibrary to protect sensitive data in Robot Framework tests.

RCC was one of the game changers with the introduction of Robotmk V2 - it takes care of the entire lifecycle of the Python environments that Robot Framework needs.

That’s super convenient, but there’s a catch: RCC assumes that the test host has access to the internet to download the required packages. This article describes a very practical way to use it in isolated environments.

The step-by-step guide updated for Checkmk 2.4 for a successful start with synthetic monitoring using Robotmk!

RCC is the command line tool used to build Python environments for the Robotmk Framework. The practical advantage of this is that it can be used both during test development and during execution by Robotmk. This ensures that the scripts always run in a reliable environment.

However, errors can sometimes occur when building or activating the environments.
This article summarizes the most common sources of errors when working with RCC and shows how to fix them efficiently.