# ERROR: invalid-extension: Official Ansible modules must have

**URL:** <https://forum.ansible.com/t/error-invalid-extension-official-ansible-modules-must-have/5719>\
**Category:** Project Discussions\
**Tags:** ansible-test\
**Created:** [May 10, 2024, 5:11am UTC](https://forum.ansible.com/t/error-invalid-extension-official-ansible-modules-must-have/5719 "2024-05-10T05:11:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [May 13, 2024, 4:03pm UTC](https://forum.ansible.com/t/error-invalid-extension-official-ansible-modules-must-have/5719/4 "2024-05-13T16:03:39Z")

</div>

We don’t really have any current plans for extending ansible-test for more flexible collection testing at this time. 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.

Our goal going forward is basically to stop adding new testing functionality for collections to ansible-test, and move the ansible-test included with core back to only testing core. Which will require that we get another team on board with forking ansible-test to solely support collections, or to implement different tooling for the long term support of collections. In theory we have this agreement in place, but no timelines, work, discussions, or architecture have happened as of yet.

---

_[View the full topic](https://forum.ansible.com/t/error-invalid-extension-official-ansible-modules-must-have/5719)._
