Bug#730530: ITP: mockldap -- mock replacement for python-ldap
Package: wnpp
Severity: wishlist
Owner: Michael Fladischer <FladischerMichael@fladi.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
* Package name : mockldap
Version : 0.1.4
Upstream Author : Peter Sagerson <psagers.pypi@ignorare.net>
* URL : http://bitbucket.org/psagers/mockldap/
* License : BSD
Programming Lang: Python
Description : mock replacement for python-ldap
This project provides a mock replacement for python-ldap. It’s useful for any
project that would like to write unit tests against LDAP code without relying on
a running LDAP server.
..
The goal of mockldap is to provide a mock instance of
LDAPObject in response to any call to ldap.initialize. In the general case, you
would register return values for all LDAPObject calls that you expect the code
under test to make. Your assertions would then verify that the tested code
behaved correctly given this set of return values from the LDAP APIs.
..
As a convenience, the mock LDAPObject isn’t just a dumb mock object. The typical
way to use mockldap is to provide some static directory content and then let
LDAPObject generate real return values. This will only work for simple LDAP
operations–this obviously isn’t a complete Python LDAP server implementation–but
those simple operations tend to cover a lot of cases.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAEBCgAGBQJSlFiTAAoJEGlMre9Rx7W2zhwP/RCxHWp53cP80HHfozo+K34j
egHUqt/VfF4i8jXuG63O2zwtzxzw8fq0kLn+kyEMPbkq0By1V8ah2LJMOx3K1vZK
RMTweHMYMRi3xZhzw44U0bg2DUOACzgHnJXN5LuCrpmOVaplwk/cOSBKYB1DP4jp
Fah/aHvrUpHQDvHZdT9lgtf6ascPx+XAeRXeGalhi4Q0fNZ3OCtdScWSzTSKSTiU
mdqrSB/Y5r8zsKkgRbGzvzixn5b4JD18SC1Y6ILwi0q4hp2ezYdvP9qEo1l2k6RF
PgfuTy4v+qaHc92TSOtvC5eOkFynB13lNKsrskI7WZ34cRfsxEJOCFbJVAtBjvne
IB2K67L2jznQMvjW4ugfJt52o2nEuBjfgRn1gIT7HCQEc3+aCP0C1qUm1BgGlabN
zZXqGNLvyyJeWbxQSmt3E5HYfcVBLZnnSDWLrCfuQdl7xFiUOwDlQ+BL+dBSMTRn
NpXqM3Cof5akeI2OmJ79MwvusH5x97B4NUu76RfCypjI8juGbeBdl+3Dss5S/jl6
TnBKySZ0s97fOcFdcIDYiqLoJsWaQq8Ovozigd0C7S9nIuZkh/5Nzs0Irdegcp8N
wR5u10fdcllLMjI4XUqWXMSAu9nWSv3wOsCgKcYN3FJa8B8+qkNX0dtoMKAJJNxx
j4qTJYVVzmcngXrh+L0P
=whci
-----END PGP SIGNATURE-----
Reply to: