test-network-modules

Playbooks for testing Ansible Network modules

For more information about using Ansible to manage your network infrastructure please see https://www.ansible.com/network

$ ansible-playbook all.yaml

To filter a set of test cases set limit_to to the name of the group, generally this is the name of the module:

$ ansible-playbook all.yaml -e "limit_to=eos_command"

To filter a singular test case set the tags options to eapi or cli, set limit_to to the test group, and test_cases to the name of the test:

$ ansible-playbook all.yaml --tags="cli" -e "limit_to=eos_command test_case=notequal"

Contributing Test Cases

Test cases are added to roles based on the module being testing. Test cases should include both cli and eapi test cases. Cli test cases should be added to role/tests/cli and eapi tests should be added to role/tests/eapi.

Conventions

• Each test case should generally follow the pattern:

  setup —> test —> assert —> test again (idempotent) —> assert —> -teardown (if needed) -> done

  This keeps test playbooks from becoming monolithic and difficult to troubleshoot.

• Include a name for each task that is not an assertion. (It's OK to add names to assertions too. But to make it easy to identify the broken task within a failed test, at least provide a helpful name for each task.)

• Files containing test cases must end in .yaml

License

Provided under the GPLv3 license.

Authors

Created and sponsored by RedHat | Ansible.