Enterprise Library Test Guide - Willy .Net

Testing the Caching Application
Block
This chapter explains how functional testing techniques were used to test the Caching
Application Block. If you have modified or extended the Caching Application
Block, you can use the same techniques and adapt the chapter’s templates and checklists
to test your own work.
Requirements for the Caching Application Block
The Caching Application Block has the following requirements:
●
●
●
●
●
●
The application block should support common caching operations such us adding
items to the cache, removing items from the cache, retrieving items from the cache,
and flushing the cache.
The application block should provide the ability to configure expiration policies.
The application block should provide the ability to cache data in persistent stores,
such as a database and isolated storage.
The application block should be extensible.
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.
These requirements must be incorporated into the design and implemented by the
code.
Selecting the Test Cases
The first step in a functional review is to verify that the design and the code support
the requirements. You do this by deciding the test cases that the design and
code must satisfy. Table 1 lists the test cases that the Caching Application Block’s
design must satisfy.