Robotmk integrates
Robot Framework into Checkmk
100% Robot Framework compatible
100% web based configuration
100% Raw data access
RobotMK contains the names of the two tools Robot Framework and CheckMK (for further details see below).
With Robot Framework you can automatically test programs, web sites (and much more...) from the perspective of the user.
Software developers appreciate this type of tests, as an application can thus for instance be tested swiftly in all its facets and variations before being released in a new version.
It is a great advantage to also have such tests in the monitoring system CheckMK and be able to check continuously...
...etc...
So far this possibility has not existed.
Now RobotMK creates a bridge and permits the integration of the results of Robot-tests into the monitoring system CheckMK.
Collect what you're interested in.
Track runtimes - on any level.
Be one step ahead before the user.
Save your time.
Comprehensive learning material
to teach you the best practices in
End2End monitoring with Checkmk and Robotmk
(Preview material - course release in autumn 2022)
You'll need a Checkmk instance in version 1.6.0pX or 2. If you want to use the bakery option, the Enterprise Edition is required. If you want to test CEE first: you can download a free version from checkmk.com which is only limited to 25 hosts.
The abstraction of the programme code into keywords is a core feature of the Robot Framework. For the computer nerds, all options remain open, as the key words can be programmed/extended and also debugged appropriately with the Python code. With Robot, the programming code forms into tools which can then also be used by non-programmers (e. g. QA teams).
Recorder functionalities as readily advertised for commercial End2End tools should be treated with caution. A test recording is only as intelligent as the purpose behind it. This means: anybody recording click-click-click will receive click-click-click. A login, for example, should always be verified too, website elements should be localized in such a way that they also withstand changes in the UX design, etc. The implementation of End2End tests means actually addressing the behaviour of the SUT (System under test).
The open source test tool ”Sakuli“, developed by Consol in 2014, has been officially phased out, as in particular the underlying web test tool “Sahi” did no longer meet modern requirements. The successor of Sakuli has appeared as a complete rewrite in version 2 (only the chargeable version allows the monitoring integration).
RobotMK was especially developed for CheckMK; the wide range of parameterization as offered by the WATO surface of RobotMK cannot be reproduced via a traditional, Nagios-compatible check-in plug (possibly one more reason to take on Checkmk….)
If the tests remain exactly the same and are not to be integrated into a monitoring system, in effect no added value is generated by Robot. The expense of integrating pure Python tests into a monitoring system should, however, not be underestimated, especially if the requirements become more complex in the course of time. Sooner or later one would rather not program and maintain oneself the complete “framework“ for integrating various test methods (Web, GUI), troubleshooting etc. Exactly here lies the strength of the Robot Framework. And hence there is RobotMK.
Robot tests allow to use the libraries in mixed-mode operation. If the login at a portal is for instance carried out with smartcard/PIN, the non-web-part can be bridged with Sikuli, the remaining test continued with selenium.
Robot can start the most common browsers in the headless mode. Pure web tests are therefore possible without logged-in user.
Professional Support is done by me and Robotmk partners.
To qualify, please scroll down this page and pick a date for a initial conversation with me. In this call, we will elaborate the main topics where you need assistance and we will find the perfect partner for your project.
This is a gift for you.
The Robotmk project owes a lot to the following companies:
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |