Hey Ansible Community ![]()
As @oranod shared in his Ansible community roadmap 2026 - Project Discussions post, one area that is of particular focus for the Community & Partner Engineering team is Developing a unified strategy for collection testing. As part of this initiative, we have identified that the first item to discuss is ansible-test.
It has been mentioned a few times by the Ansible Core team here on the Forum [1] [2] that there are no plans for new testing functionality for collections in ansible-test or to extend ansible-test to be more flexible for collection testing. Furthermore, as Sivel mentioned in his post, ansible-test was never actually designed for collection testing:
"The original reason that ansible-test became the standard for testing collections was largely because nothing else existed, so collections inherited the same rules as ansible-core.β
Right now the Ansible documentation contradicts this messaging, so our first item is to update the documentation to explicitly state that ansible-test is not a tool for collection testing. We want to stress that the purpose of this is not to say collection maintainers should stop using ansible-test for testing collections at this time, we are updating the documentation to clarify the purpose of ansible-test.
In the next two weeks we will be sharing another update to kick off the unified strategy for collection testing, outlining some goals of the initiative and providing an overview of the current collection testing landscape so weβre all on the same page and in a good place to begin further discussions on this area. Please keep an eye out for this upcoming post and the collection-test-strat tag.
[1]: ERROR: invalid-extension: Official Ansible modules must have - #4 by sivel - Project Discussions
[2]: CfgMgmtCamp 2026 discussion (7/12): Collection testing is still a mess - #3 by sivel