summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJoshua Harlow <harlowja@yahoo-inc.com>2014-05-07 12:59:14 -0700
committerJoshua Harlow <harlowja@yahoo-inc.com>2014-05-07 12:59:14 -0700
commit9cce4a9d3b9d333d3d3e9d2d09f83378b1b8b46b (patch)
treed674ecaede57e2fa3c1c70d920c66cc0d2628d2c /docs
parent723a5c2165b8fcc21332e459a3def31b28f0994f (diff)
downloadkazoo-9cce4a9d3b9d333d3d3e9d2d09f83378b1b8b46b.tar.gz
Add docs for kazoo + zake usage for those that are interested
Add a description and link to the zake library (and its repo) for those that want to test kazoo client-level functionality without having to setup a full zookeeper runtime to accomplish this. Part of #198
Diffstat (limited to 'docs')
-rw-r--r--docs/testing.rst16
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/testing.rst b/docs/testing.rst
index 085ab43..5f22bf4 100644
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -66,3 +66,19 @@ one above:
self.client.ensure_path('/test/path')
result = self.client.get('/test/path')
...
+
+Zake
+====
+
+For those that do not need (or desire) to setup a zookeeper runtime to test
+integration with kazoo there is also a under developement library
+called `zake`_. Its code and repository can be found
+`here <https://github.com/yahoo/Zake>`_ (contributions welcome). It can be used
+to provide a *fake client* to layers of your application that interact
+with kazoo (using the same client interface) during testing to allow for
+introspection of what was stored, which watchers are active (and more) after
+your test of your application code has finished (this style of introspection
+is hard to when directly interfacing with zookeeper via a non-fake kazoo
+client).
+
+.. _zake: https://pypi.python.org/pypi/zake/