Enterprise Library Test Guide - Willy .Net

102
Enterprise Library Test Guide
Selecting the Test Cases
The first step in a functional review is to make sure that the design and the code support
these requirements. You do this by deciding the test cases that they must satisfy
so that the application block fulfills all its requirements.
Table 1 lists the test cases that the application block’s design must satisfy.
Table 1: Security Application Block Design Cases
Priority
High
High
High
High
High
High
High
High
High
High
Design test case
Verify that the application block can be extended with custom authorization providers
and custom security cache providers.
Verify that there is a consistent approach to creating authorization providers and security
cache providers.
Verify that the application block provides a simple method to perform authorization.
Verify that the application block provides simple methods to save, expire, and retrieve
an identity from a caching store.
Verify that the application block implements the standard provider model for authorization
and security-related operations.
Verify that the ability to create the application block’s domain objects from the configuration
data follows the Dependency Injection pattern.
Verify that the application block can retrieve configuration data from different sources,
such as an application configuration file, a database, or from memory.
Verify that the instrumentation is implemented with loosely coupled events.
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 the custom
authorization providers and custom caching stores.
After you identify the design issues, you should do the same for the code. Table 2
lists the test cases that the Security Application Block code must satisfy.
Table 2: Security Application Block Code Test Cases
Priority
High
High
High
High
High
Code test case
Verify that the application block creates one instance of the AuthorizationProvider
class for each request.
Verify that the application block only creates one instance of the SecurityCacheProvider
class for the specified instance name.
Verify that the assembler classes that implements the IAssembler interface create the
authorization providers and the security cache providers, and verify that the assembler
classes inject the configuration object values into those domain objects.
Verify that the configuration properties of the authorization and security cache providers
are exposed as public and that they are strongly typed.
Verify that the configuration properties for the custom providers are exposed as public
and that they are implemented as custom property collections.