summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMonty Taylor <mordred@redhat.com>2016-11-18 08:51:28 -0600
committerDavid Shrewsbury <Shrews@users.noreply.github.com>2016-11-18 09:51:28 -0500
commit9914626ce2dda7892119443e7ae95d71058345e5 (patch)
tree8718fce8ab84abd1762f931c92a17ff8c0d73684
parent2a9ddb1c70cab02af8341f674265384af250452b (diff)
downloadansible-modules-core-9914626ce2dda7892119443e7ae95d71058345e5.tar.gz
Add a few lines about testing (#5662)
-rw-r--r--cloud/openstack/README.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/cloud/openstack/README.md b/cloud/openstack/README.md
index 4a872b11..36cdcd38 100644
--- a/cloud/openstack/README.md
+++ b/cloud/openstack/README.md
@@ -54,3 +54,11 @@ Libraries
users as a primary audience, they are for intra-server communication. The
python-openstacksdk is the future there, and shade will migrate to it when
its ready in a manner that is not noticable to ansible users.
+
+Testing
+-------
+
+* Integration testing is currently done in OpenStack's CI system in
+ http://git.openstack.org/cgit/openstack-infra/shade/tree/shade/tests/ansible
+* Testing in shade produces an obvious chicken-and-egg scenario. Work is under
+ way to trigger from and report on PRs directly.