Enterprise Library Test Guide - Willy .Net

Testing the Logging Application
Block
This chapter explains how functional testing techniques were used to test the Logging
Application Block. If you have modified or extended the Logging Application
Block, you can use the same techniques and adapt the chapter’s templates and checklists
to test your own work.
Requirements for the Logging Application Block
The Logging Application Block has the following requirements:
●
●
●
●
●
●
●
●
The application block should be extensible.
The application block should support common logging operations.
The application block should be able to distribute logging information to multiple
sources.
The application block should support tracing to mark the start and end of an
activity.
The trace listeners, filters, and formatters 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.
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.