Enterprise Library Test Guide - Willy .Net

Testing the Security Application
Block
This chapter explains how functional testing techniques were used to test the Security
Application Block. If you have modified or extended the Security Application
Block, you can use the same techniques and adapt the chapter’s templates and checklists
to test your own work.
Requirements for the Security Application Block
The Security Application Block has the following requirements:
●
●
●
●
●
●
●
●
The application block should be extensible.
The application block should provide a simple interface for authorization operations.
The application block should provide a simple interface for saving, expiring, and
retrieving the identity from a caching store.
The application block should provide a standard provider model for authorization
and security-related caching.
Authorization providers and security cache providers should be configurable.
The application block should be able to read configuration information from any
configuration source, such as an XML file or a database.
The application block should support configurable instrumentation, including
WMI (Windows Management Instrumentation), performance counters, and event
logs.
The application block should work with desktop applications and with Web
applications.
These requirements must be incorporated into the design and implemented by the
code.