community-topics
community-topics copied to clipboard
ansible-community
Revamping the pytest-ansible plugin
Summary
The idea is to club pytest-ansible, pytest-molecule, pytest-ansible-units into just one pytest-ansible plugin, pick the necessary features we need from each plugin, add the features which are missing/the ones we need and make the pytest-ansible plugin a common package for all the unit-testing work.
As we move ahead with this approach, we need your suggestions if this would be the right thing to do or feel free to drop in any other suggestions you may have.
If this idea gets approved, the next steps that we would be following would be:
- create a new branch in the pytest-ansible repository and rename master branch to main
- make a new release 2.2.5 before starting off with our changes so that the users who are using the plugin wouldnt be affected plus we would be having a stable release and users can continue using that and after we are done with our changes we can make a new release that is 3.0.0
We are looking forward to the suggestions from the people who are actively using this plugin and from the community members.
Additional Information
No response
We just started using pytest-ansible-units today in https://github.com/ansible-collections/pravic/pull/3. The main reasons for using this is that local development is easier. Testing startup is faster, we have direct control over pytest and it's easier to drop into a debugger. I love seeing the work being done to make testing ansible with pytest easier.
I haven't used any of the three projects, but this sounds like a good idea to me.
One thing that would be great would be if pytest-ansible would stop depending on Ansible, but depend on ansible-core instead (or alternatively allow the user to install whatever they want, if you want to support Ansible 2.9 and ansible-base 2.10 as well).
Updated information here: https://github.com/ansible-community/pytest-ansible/issues/73
Things are progressing nicely
@Ruchip16 Please close this issue if done, or open a new forum topic and then close the issue with a pointer to the new discussion: Community-topics: Archiving the repo
@Ruchip16 feel free to recreate the topic on the forum as @mariolenz mentioned, closing, thanks everyone!
