| 1 |
Source: mockldap |
| 2 |
Section: python |
| 3 |
Priority: optional |
| 4 |
Maintainer: Debian Python Team <[email protected]> |
| 5 |
Uploaders: |
| 6 |
Michael Fladischer <[email protected]>, |
| 7 |
Build-Depends: |
| 8 |
debhelper-compat (= 13), |
| 9 |
dh-sequence-python3, |
| 10 |
python3-all, |
| 11 |
python3-doc, |
| 12 |
python3-funcparserlib, |
| 13 |
python3-pyldap, |
| 14 |
python3-setuptools, |
| 15 |
python3-sphinx, |
| 16 |
Rules-Requires-Root: no |
| 17 |
Standards-Version: 4.6.1 |
| 18 |
Homepage: https://bitbucket.org/psagers/mockldap/ |
| 19 |
Vcs-Git: https://salsa.debian.org/python-team/packages/mockldap.git |
| 20 |
Vcs-Browser: https://salsa.debian.org/python-team/packages/mockldap |
| 21 |
Testsuite: autopkgtest-pkg-python |
| 22 |
|
| 23 |
Package: python-mockldap-doc |
| 24 |
Section: doc |
| 25 |
Architecture: all |
| 26 |
Depends: |
| 27 |
${misc:Depends}, |
| 28 |
${sphinxdoc:Depends}, |
| 29 |
Multi-Arch: foreign |
| 30 |
Description: simple mock implementation of python-ldap (Documentation) |
| 31 |
This project provides a mock replacement for python-ldap. It’s useful for any |
| 32 |
project that would like to write unit tests against LDAP code without relying |
| 33 |
on a running LDAP server. |
| 34 |
. |
| 35 |
The goal of mockldap is to provide a mock instance of LDAPObject in response to |
| 36 |
any call to ldap.initialize. In the general case, you would register return |
| 37 |
values for all LDAPObject calls that you expect the code under test to make. |
| 38 |
Your assertions would then verify that the tested code behaved correctly given |
| 39 |
this set of return values from the LDAP APIs. |
| 40 |
. |
| 41 |
As a convenience, the mock LDAPObject isn’t just a dumb mock object. The |
| 42 |
typical way to use mockldap is to provide some static directory content and |
| 43 |
then let LDAPObject generate real return values. This will only work for simple |
| 44 |
LDAP operations–this obviously isn’t a complete Python LDAP server |
| 45 |
implementation–but those simple operations tend to cover a lot of cases. |
| 46 |
. |
| 47 |
This package contains the documentation. |
| 48 |
|
| 49 |
Package: python3-mockldap |
| 50 |
Architecture: all |
| 51 |
Depends: |
| 52 |
python3-ldap, |
| 53 |
${misc:Depends}, |
| 54 |
${python3:Depends}, |
| 55 |
Suggests: |
| 56 |
python-mockldap-doc, |
| 57 |
Description: simple mock implementation of python-ldap (Python3 version) |
| 58 |
This project provides a mock replacement for python-ldap. It’s useful for any |
| 59 |
project that would like to write unit tests against LDAP code without relying |
| 60 |
on a running LDAP server. |
| 61 |
. |
| 62 |
The goal of mockldap is to provide a mock instance of LDAPObject in response to |
| 63 |
any call to ldap.initialize. In the general case, you would register return |
| 64 |
values for all LDAPObject calls that you expect the code under test to make. |
| 65 |
Your assertions would then verify that the tested code behaved correctly given |
| 66 |
this set of return values from the LDAP APIs. |
| 67 |
. |
| 68 |
As a convenience, the mock LDAPObject isn’t just a dumb mock object. The |
| 69 |
typical way to use mockldap is to provide some static directory content and |
| 70 |
then let LDAPObject generate real return values. This will only work for simple |
| 71 |
LDAP operations–this obviously isn’t a complete Python LDAP server |
| 72 |
implementation–but those simple operations tend to cover a lot of cases. |
| 73 |
. |
| 74 |
This package contains the Python 3 version of the library. |