ansible.builtin.junit – write playbook output to a JUnit file.
Note
This callback plugin is part of ansible-core and included in all Ansible
installations. In most cases, you can use the short
plugin name
junit even without specifying the collections: keyword.
However, we recommend you use the FQCN for easy linking to the
plugin documentation and to avoid conflicting with other collections that may have
the same callback plugin name.
Synopsis
This callback writes playbook output to a JUnit formatted XML file.
Tasks show up in the report as follows: ‘ok’: pass ‘failed’ with ‘EXPECTED FAILURE’ in the task name: pass ‘failed’ with ‘TOGGLE RESULT’ in the task name: pass ‘ok’ with ‘TOGGLE RESULT’ in the task name: failure ‘failed’ due to an exception: error ‘failed’ for other reasons: failure ‘skipped’: skipped
Requirements
The below requirements are needed on the local controller node that executes this callback.
whitelist in configuration
junit_xml (python lib)
Parameters
Parameter |
Comments |
|---|---|
Consider any tasks reporting “changed” as a junit test failure Default: “no” Configuration:
|
|
Consider failed tasks as a junit test failure even if ignore_on_error is set Default: “no” Configuration:
|
|
Hide the arguments for a task Default: “no” Configuration:
|
|
Should the setup tasks be included in the final report Default: “yes” Configuration:
|
|
Directory to write XML files to. Default: “~/.ansible.log” Configuration:
|
|
Configure the output to be one class per yaml file Default: “no” Configuration:
|
|
Configure the output to use relative paths to given directory Default: “none” Configuration:
|
|
Consider a task only as test case if it has this value as prefix. Additionaly failing tasks are recorded as failed test cases. Default: “\u003cempty\u003e” Configuration:
|