What is RobotMK?


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...

  • ...whether the login into the CRM system functions – and how long it takes
  • ....whether the search function in the SAP/merchandise management system for randomly selected article numbers works
  • ...how efficiently the ordering process functions in the web shop

...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.

Runtime metric graphs

Collect what you're interested in.

Which elements of a Robot test (suites, tests, keywords) are to be recorded in CheckMK-graphs, can be determined via a sophisticated, pattern-based rule system.
After all, the whole is expected to remain clearly structured.

Runtime monitoring

Track runtimes - on any level.

In RobotMK the runtimes of all test elements are available for evaluation.
Here too, pattern based WATO rules allow to set runtime thresholds of Robot suites, tests and keywords.

Detect functional disruptions

Be one step ahead before the user.

It is simply too late if your customer notices that a button in your business application is not visible.
Robot Framwork is the "automated user": it continuously checks the user interfaces of SAP, CRM, Intranet, Website etc. for its usability.
With Robotmk, Robot-Tests can be parametrized dynamically using data sources like CSV, XLS/XLSX, MS PICT etc. to achieve test coverage at its best.
You don't see anything here, this is correct :-)

Features

Why you should decide for the "lingua franca" of test automation.

  • Central control via WATO

    RobotMK is configured via a powerful rule system in the web administration interface of CheckMK (WATO).

  • Flexible output formatting

    RobotMK evaluates intricately interleaved Robot results; the pattern-based reduction of the output to the essential ensures an optimum result.

  • Readbility

    The "keyword-driven" approach abstracts complex Python code and can be encapsulated at will – with free name choice.
    The result: traceable results and meaningful messages in the monitoring system.

  • 100% Robot compatible

    RobotMK does not require any adaptation to existing Robot tests; every Robot test can be integrated in CheckMK without any intervention.

  • Performance monitoring

    RobotMK can monitor runtimes at any level, be it whole suites, tests and keywords.
    (Or how would you detect an insidious login time increase by 0.1s per month?)

  • Worthwhile addition to CheckMK

    Checkmk can only monitor up to OSI layer 7. Robotmk completes your monitoring with a detailled view inside applications to get a holistic view of services and their quality.

  • Swiss army knife

    The Library concept makes Robot Framework the Suisse pocket knife. You'll find a library for nearly any use case. And you are free to use them combined in a test.

  • Strong community

    Great if you have backed the right horse, in case help is required: CheckMK and Robot have a worldwide, English speaking community at their disposal.

  • Platform-independent

    One for all: Robot Framework works for all common platforms: Windows, Linux, MacOS, Android, iOS, ... including the appropriate test libraries in each case (e.g. Auto-IT for Windows automation).

  • 100% Open Source

    RobotMK - like Robot Framework and CheckMK Raw – is published as an Open Source project. No hidden costs, no vendor-lock-in.

FAQ

  • What do I need to get started with Robotmk?

    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.

  • For me as programmer, the keywords of Robot look rather strange. How flexible can one be with them?

    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).

  • Is there a recording function for End2End tests?

    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).

  • What has become of Sakuli v1?

    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).

  • Can I also employ RobotMK in other monitoring systems (Nagios, Naemon, Icinga, Zabbix, Groundworks, Centreon, ...)?

    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….)

  • So far I have written my selenium tests in Python. What reason should I have to change over to the Robot Framework?

    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.

  • My web application requires interaction with the desktop. Can I use selenium together with Sikuli for example?

    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.

  • Does the test client have to remain unlocked to be able to carry out End2End tests?

    Robot can start the most common browsers in the headless mode. Pure web tests are therefore possible without logged-in user.

  • Where can I get professional support?

    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.

Get your free call

This is a gift for you.

My offer is to listen to your situation and challenges in a free 1h-call via Zoom.

This is your chance to get all your questions answered and an estimation about the next steps - with or without me.

I speak German and fluent English.
(Make sure to select the correct time zone.)

Sponsors

The Robotmk project owes a lot to the following companies:

Checkmk
GOLD Partner
Checkmk
GOLD Partner
Checkmk
GOLD Partner