Enterprise Library Test Guide - Willy .Net

Testing the Security Application Block 105
Design test case Implemented? Feature that implements design
Verify that the
instrumentation
uses loosely coupled
events.
Yes
The methods in the SecurityCacheProviderInstrumentationProvider
class and the AuthorizationProviderInstrumentationProvider
class raise the events
that bind to the methods in the SecurityCacheProviderInstrumentationListener
class and the AuthorizationProviderInstrumentationListener
class
respectively during run time.
Verify that situations
that can cause
exceptions are
addressed and that
the application block
logs the exceptions
through the instrumentation.
Verify that the
application block
supports custom
property collections
for custom security
cache providers and
for custom authorization
providers.
Yes
Yes
For example, both the CachingStoreProvider class
and the AuthorizationRuleProvider class include
the InstrumentationProvider property. This property
retrieves the instrumentation provider that defines
the events for the security cache and the authorization
provider. The provider logs the events to WMI
and the event log.
The CustomAuthorizationProviderData class
and the CustomSecurityCacheProviderData class
support custom property collections for custom
providers.
After the code is implemented, you can review it to see if it satisfies its test cases.
Table 4 lists the results of a code review for the Security Application Block.
Table 4: Security Application Block Code Verification
Code test case Implemented? Feature that is implemented
Verify that, for
each request,
the application
block only
creates one
instance of
a class that
derives from
the AuthorizationProvider
or that
implements
the IAuthorizationProvider
interface.
Yes
The AuthorizationFactory class creates instances of classes
that derive from the AuthorizationProvider class as well as instances
of classes that implement the IAuthorizationProvider
interface. It does this by calling the AuthorizationProviderFactory
class. The AuthorizationProviderFactory class derives
from the NameTypeFactoryBase class. This class creates a
new instance of a provider for every request. This derivation is
shown in the following code.
public class AuthorizationProviderFactory : NameTyp
eFactoryBase{}
continued