Tests on DomainSpecificLDAPandSQLIdentity cannot create and use new domains

[Samuel de Medeiros Queiroz]

Tests in this class (or in subclasses) can create domains, but cannot use them for any identity operation, such as list_users.

When domain-specific backends functionality is used, the created domains (that do not have an explicit configuration) are mapped in the default driver. It works pretty well when the default driver is SQL, but not for LDAP, which is read-only.

LDAP is configured as default driver for that test class.

An exception is thrown when trying to use identity operations on that domain, since the manager cannot find a driver to use:

        Found multiple domains being mapped to a driver that does not support that (e.g. LDAP) - Domain ID: fcda5a65a54e43618b1c5acfaefa8d00, Default Driver: True

[Henry Nash (henry-nash)]

I don't think this is a bug - that's the point of this test class....no additional domains are allowed - it's a restrictive setup. We could argue that this is not a valid test case, in which case we should delete the class entirely.

[Steve Martinelli (stevemar)]

I agree with Henry, I do not believe this is a bug. Additionally, we do not need to use bug reports for test refactorings.