Currently the CI configuration in Travis purely just checks the syntax and sees that the code is written as per Ansible's best practices. We need to enhance this to provide proper end to end testing and verify that the module is really working properly on the supported OSs
Currently the CI configuration in Travis purely just checks the syntax and sees that the code is written as per Ansible's best practices. We need to enhance this to provide proper end to end testing and verify that the module is really working properly on the supported OSs