From 4d78c784a6743b9c3aad03cb602d4b505f73303a Mon Sep 17 00:00:00 2001 From: jctanner Date: Mon, 28 Nov 2016 21:26:14 -0500 Subject: [PATCH] Add a doc reference to the module developer guide. (#18658) Addresses https://github.com/ansible/ansible-modules-core/issues/5672 --- docsite/rst/community.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docsite/rst/community.rst b/docsite/rst/community.rst index 854edc9dfc..bfaac87677 100644 --- a/docsite/rst/community.rst +++ b/docsite/rst/community.rst @@ -147,6 +147,9 @@ Note that we do keep Ansible to a particular aesthetic, so if you are unclear ab is a good fit or not, having the discussion on the development list is often a lot easier than having to modify a pull request later. +New module developers should read through `http://docs.ansible.com/ansible/dev_guide/developing_modules.html`_ for helpful pointers +and information about running adhoc tests `http://docs.ansible.com/ansible/dev_guide/developing_modules.html#testing-modules`_. + When submitting patches, be sure to run the unit tests first ``make tests`` and always use, these are the same basic tests that will automatically run on Shippable when creating the PR. There are more in depth tests in the ``tests/integration`` directory, classified as destructive and non_destructive, run these if they pertain to your modification. They are set up