Dear Monks
In May 2003, after some discussions here and in the perl-ldap list, I published Net::LDAP::Express.
One month ago, I finally published a small amount of changes that were lying around in my hard disk since months, added a patch provided by a user (thanks Gordon!) and deeply revised the test suite.
To cut a long story short, the test suite of the module can simply check if its prerequisite modules are there, or do deeper checks, trying to create and modify entries in the directory server.
Unfortunately, from the reports I had when I uploaded v0.10 (that had a broken test suite) it seems that CPAN testers are doing just the short tests, so I don't know if the deeper tests work fine in environments different from OpenLDAP.
If anybody of you would be so kind to do the deeper tests on the same and, if possible, different environment (like, e.g.: Active Directory, Novell...) and post some report, I would greatly apreciate it.
For those of you that are willing to test, the relevant part of the README file follows.
TESTING THE SOURCE
This module's tests require that you have access to a directory server
to test the functionalities. If you don't set some environment
variables before running "make test", the tests will just check for a
correct installation of the module and for the presence of some other
modules that Net::LDAP::Express depends upon.
To effectively run the tests just prepend to "make test" a sensible
assignment to the TEST_HOST environment variable assignment, like in
TEST_HOST='ldap.server.com' make test
This will run the tests contacting the directory server at
ldap.server.com. If the server runs on a non-standard port just add a
TEST_PORT variable:
TEST_HOST='ldap.server.com' TEST_PORT=1389 make test
The scripts will try to use ou=simple,o=test as their base subtree
(the ou=simple is there because the module was supposed to be called
Net::LDAP::Simple in the beginning). If you want to change it, just
use a TEST_BASE environment variable with the base subtree of your
choice. The tree you use as TEST_BASE will be added a ou=test subtree
and the tests will take place there. Feel free to get rid of it when
the tests are finished.
Some tests will try to create and modify entries on the directory
server, and this requires some privileges. The test script will use
cn=admin,o=test as bind DN and "secret" as password; again, if this
isn't the case you can simply prepend an assignment to TEST_BINDDN and
TEST_BINDPW.
Thanks in advance
Ciao!
--bronto
In theory, there is no difference between theory and practice. In practice, there is.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
