Releases: elabit/robotmk
Releases · elabit/robotmk
v2.0.0-alpha
This is a test build not intended for public use.
Release v1.4.2
Release v1.4.1
Fixed
- agent plugin: fixed bug when piggyback was set, runner crashed
Release v1.4.0
Changed
- The Robotmk mechanism behind the RF parameter
--exitonfailure
has been optimized and clearly documented in the inline help. If this option was set, the remaining tests that were not executed were previously marked as FAIL or CRITICAL. This is the default in Robot Framework (see RF user guide), but in Checkmk it lead to an alarm not only for the root cause (the failed test), but also for the subsequent errors.
The behavior of Robotmk has been slightly modified in that the tests omitted due to a previous failure are filtered out and not passed to Checkmk for evaluation anymore. Tests that have not been executed become "stale", and false alarms are thus avoided. (Thanks for the valuable feedback.)
Release v1.3.1
Fixed
robotmk-runner.py
crashed when no re-execution strategy was set at all (closes #209)
Release v1.3.0
Added
- Bakery/Check Plugin: Introduced
complete
as new re-execution mode for suites (#206). This is useful for suites that must always run completely because the tests depend on each other. Thus, a suite OK result is returned not when each test was OK in an arbitrary iteration, but rather in a common iteration.
Changed
- Bakery: Introduced "incremental" as a name for the previous re-execution mode.
⚠️ Your existing rules are compatible with that new naming scheme - but they are only saved in the new format after they have been opened and saved (even if there are no changes).
Release v1.2.10-beta-1
Added
- Documentation: Added FAQs with design decisions
- Check: Added the possibility to temporarily skip the execution of suites by placing a
DISABLED
(case sensitive) file in the suite's root folder. (#192)
Robotmk will silently ignore this suite as long the DISABLED file is there.
(Thanks Marcus for this suggestion - this is the perfect alternative to commenting out the suite inrobotmk.yml
manually).
You can also optionally write a reason ("Need a short break.") into the file; it will get logged in Robotmk's log:
2022-08-02 22:25:28,449 RMKrunner [48887] INFO: ####################
2022-08-02 22:25:28,575 RMKrunner [48887] INFO: => Suites to start: sleep
2022-08-02 22:25:28,583 RMKrunner [48887] INFO: ~~~~ Suite ID: sleep ~~~~
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: Suite 'sleep' is skipped because of the 'DISABLED' flagfile in its suite folder. Reason: Need a short break.
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: (Be aware that the services in Checkmk will become stale soon.)
2022-08-02 22:25:28,595 RMKrunner [48887] INFO: ... Quitting Runner, bye. ---
Changed
- Bakery rule: Lowered the log retention threshold (#172)
- Check: Fixed a bug which lead to metric names without specials chars like umlauts => metric names can slightly change, sorry. (#197)
Fixed
- Bakery (V2): Added missing
timeout
to async robotmk execution.timeout
is now
set to 5 sec less than the execution interval so that the agent can kill the runner
before the next execution. (#203) - Check: Creates host dir for HTML logs; updated inline help for HTML log icons (#201)
- Check: Allow only 1 runtime threshold by setting the other one to 0 (#198)
Removed
Deprecated
Release v1.2.10-beta
Added
- Documentation: Added FAQs with design decisions
- Check: Added the possibility to temporarily skip the execution of suites by placing a
DISABLED
(case sensitive) file in the suite's root folder. (#192)
Robotmk will silently ignore this suite as long the DISABLED file is there.
(Thanks Marcus for this suggestion - this is the perfect alternative to commenting out the suite inrobotmk.yml
manually).
You can also optionally write a reason ("Need a short break.") into the file; it will get logged in Robotmk's log:
2022-08-02 22:25:28,449 RMKrunner [48887] INFO: ####################
2022-08-02 22:25:28,575 RMKrunner [48887] INFO: => Suites to start: sleep
2022-08-02 22:25:28,583 RMKrunner [48887] INFO: ~~~~ Suite ID: sleep ~~~~
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: Suite 'sleep' is skipped because of the 'DISABLED' flagfile in its suite folder. Reason: Need a short break.
2022-08-02 22:25:28,591 RMKrunner [48887] WARNING: (Be aware that the services in Checkmk will become stale soon.)
2022-08-02 22:25:28,595 RMKrunner [48887] INFO: ... Quitting Runner, bye. ---
Changed
- Bakery rule: Lowered the log retention threshold (#172)
- Check: Fixed a bug which lead to metric names without specials chars like umlauts => metric names can slightly change, sorry. (#197)
Fixed
- Bakery (V2): Added missing
timeout
to async robotmk execution.timeout
is now
set to 5 sec less than the execution interval so that the agent can kill the runner
before the next execution. (#203) - Check: Creates host dir for HTML logs; updated inline help for HTML log icons (#201)
- Check: Allow only 1 runtime threshold by setting the other one to 0 (#198)
Removed
Deprecated
Release v1.2.9
Fixed
- Check: Changed folder for HTML logs from local to var
Release v1.2.8
- Check: Fixed #189 - Critical threshold / value not transferred to perfdata