From b9b9739086d4ca0b481877c831c2f47e85dccc73 Mon Sep 17 00:00:00 2001 From: Hanno Schlichting Date: Fri, 6 Jun 2014 13:12:17 +0200 Subject: Tweak Zake description and add changelog entry, closes #198. --- docs/testing.rst | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) (limited to 'docs') diff --git a/docs/testing.rst b/docs/testing.rst index 5f22bf4..1051be7 100644 --- a/docs/testing.rst +++ b/docs/testing.rst @@ -70,15 +70,12 @@ one above: 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 `_ (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/ +For those that do not need (or desire) to setup a Zookeeper cluster to test +integration with kazoo there is also a library called +`zake `_. Contributions to +`Zake's github repository `_ are welcome. + +Zake can be used to provide a *mock 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. -- cgit v1.2.1