summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCharles-Henri de Boysson <ceache@users.noreply.github.com>2020-04-07 23:35:58 -0400
committerCharles-Henri de Boysson <ceache@users.noreply.github.com>2020-04-14 23:20:32 -0400
commitde97d74b50b62cd2f0cddc2a04e150575d9c6bc7 (patch)
tree4964414f500e5326f44f68b8623f2ff532e6c41b /docs
parenta636d7a6bb88ab9080e902983b10c8f0f1bf60a8 (diff)
downloadkazoo-de97d74b50b62cd2f0cddc2a04e150575d9c6bc7.tar.gz
feat(test): Move to pytest
Diffstat (limited to 'docs')
-rw-r--r--docs/testing.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/testing.rst b/docs/testing.rst
index 1051be7..c98e35a 100644
--- a/docs/testing.rst
+++ b/docs/testing.rst
@@ -7,7 +7,7 @@ Testing
Kazoo has several test harnesses used internally for its own tests that are
exposed as public API's for use in your own tests for common Zookeeper cluster
management and session testing. They can be mixed in with your own `unittest`
-or `nose` tests along with a `mock` object that allows you to force specific
+or `pytest` tests along with a `mock` object that allows you to force specific
`KazooClient` commands to fail in various ways.
The test harness needs to be able to find the Zookeeper Java libraries. You