Distribute Robot checks with CheckMK Agent bakery

[simonmeggle]

No description provided.

[simonmeggle]

WIP in branch bakery

[simonmeggle]

Proposal for Robot arguments which should be supported in the bakery rule and the agent plugin:

Must-be:

• --name: Set the name of the top level suite. Overrides auto naming from top level dir or robot file.
• --suite: Select suites by name pattern
• --test: Select tests by name pattern
• --include: Select tests by tag pattern (exists already -> rename)
• --exclude: Exclude tests by tag pattern
• --variablefile: Load variables from file
• --exitonfailure=True: lets RF exit the whole suite if one test failed. (default is to execute all tests)

Optional:

• --critical/--noncritical - pattern which tests are considered critical = can raise exceptions.

[simonmeggle]

#27 describes how the bakery could clone the test repository and bake the test files into the agent.

[mike1098]

This is done with agent bakery rule "Deploy custom files with agent". Tested and works.

[simonmeggle]

What I wanted to remark is the possibility to include a version controlled test dir. For now it is ok to deliver the files with the existent bakery rule you mentioned.

[simonmeggle]

@guillaume-durville : argumentfile is not a valid parameter when calling robot via python. I just have seen this.
Options that do not take an argument (like exitonfailure) are given as boolean parameters: exitonfailure=True

[simonmeggle]

I have now written tests for the agent plugin and almost each possible robot argument (see above).
For reference, you can inspect the robotmk.yml files for each test/argument in https://github.com/simonmeggle/robotmk/tree/agentplugin/test/fixtures/plugin.

[simonmeggle]

(already solved)