[Mono-devel-list] Tests for System.DirectoryServices

Sébastien Pouliot spouliot at videotron.ca
Tue Apr 5 13:50:58 EDT 2005

Hello Boris,

> I understand that use of machine.config or app.config is far from ideal,
> but at least it can provide us with a basic solution.

When things gets too complicated people quit. I don't think many people are
gonna be runned the LDAP tests but I wouldn't want to discourage anyone. So
the easier the better ;-)

Why don't keep the environment variable (very simple) and point it to a
configuration file (XML or plain ASCII) ?

That would mean:

* that, by default, all non-network tests in System.DirectoryServices.dll
will be executed (here I'm thinking about the few permissions tests already
present _and_ future CAS tests);

* it would be possible to check into SVN a configuration sample file that
any user can copy (so it won't get in conflict with SVN) and edit;

* it would be possible to have multiple configuration files, e.g. if you
want to test against different LDAP servers (machine or software);

* all configuration could be done in a single place whatever the
runtime/version you are using.

> Do you think there is a better way to provide a "default" behavior,
> either at DirectoryServices or Ldap level, such that it will be easily
> configured for each client application?
> The trivial solution - default is "LDAP://localhost:389", does not looks
> satisfactory and, in addition, does not provides a solution for base dsn.

Without a valid configuration file I would simply ignore all tests
(requiring a server). This is similar to what I'm doing for the CAS tests.
If someone doesn't exclude them (default for "make run-test") and doesn't
supply --security to the mono runtime, then they are all ignore (and nicely
nunit still shows them as ignored when they aren't excluded).

Sebastien Pouliot
home: spouliot at videotron.ca
blog: http://pages.infinit.net/ctech/poupou.html

More information about the Mono-devel-list mailing list