Enterprise Library Test Guide - Willy .Net

Testing the Exception Handling
Application Block
This chapter explains how functional testing techniques were used to test the Exception
Handling Application Block. If you have modified or extended the Exception
Handling Application Block, you can use the same techniques and adapt the chapter’s
templates and checklists to test your own work.
Requirements for the Exception Handling Application Block
The Exception Handling Application Block has the following requirements:
●
●
●
●
●
●
The application block should support commonly used exception handling
operations, such as logging the exceptions, replacing the original exception with
another exception and wrapping the original exception with another exception.
The application block should be able to combine the exception handlers. For
example, it should be possible to log the exception information and then replace
the original exception with another.
The application block should support configurable instrumentation, including
WMI (Windows Management Instrumentation), performance counters, and event
logs.
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 work with desktop applications and with Web
applications.
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 make sure that the design and the code
support these requirements. You do this by deciding the test cases that the design
and code must satisfy. Table 1 lists the test cases that the application block’s design
must satisfy.