mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
d6e2f1846a
* wip: add a unit test for playbook/base.py This commit include a failing test TestBaseSubClass.test_attr_class_post_validate It fails with the error: Traceback (most recent call last): File "/home/adrian/src/ansible/test/units/playbook/test_base.py", line 264, in test_attr_class_post_validate bsc = self._base_validate(ds) File "/home/adrian/src/ansible/test/units/playbook/test_base.py", line 206, in _base_validate bsc.post_validate(templar) File "/home/adrian/src/ansible/lib/ansible/playbook/base.py", line 450, in post_validate " Error was: %s" % (name, value, attribute.isa, e), obj=self.get_ds()) AnsibleParserError: the field 'test_attr_class_post_validate' has an invalid value (<class 'units.playbook.test_base.ExampleSubClass'>), and could not be converted to an class. Error was: test_attr_class_post_validate is not a valid <class 'units.playbook.test_base.ExampleSubClass'> (got a <class 'ansible.playbook.base.BaseMeta'> instead) * wip, test refactoring * wip, trying to add a parent->child * wip, fix isa=class. the ds the base using needs an instance of the class (ie, whats normally created by the yaml loaders) * wip, theres no need to argue, I just dont understand parents * stub a _preprocess_data for coverage * cleanup, required, parent, etc |
||
---|---|---|
.. | ||
integration | ||
samples | ||
sanity | ||
units | ||
utils | ||
README.md |
Ansible Test System
Folders
units
Unit tests that test small pieces of code not suited for the integration test layer, usually very API based, and should leverage mock interfaces rather than producing side effects.
Playbook engine code is better suited for integration tests.
Requirements: sudo pip install paramiko PyYAML jinja2 httplib2 passlib nose mock
integration
Integration test layer, constructed using playbooks.
Some tests may require cloud credentials, others will not, and destructive tests are separated from non-destructive so a subset can be run on development machines.
learn more
hop into a subdirectory and see the associated README.md for more info.