Enterprise Library Test Guide - Willy .Net

Testing the Data Access Application
Block
This chapter explains how functional testing techniques were used to test the Data
Access Application Block. If you have modified or extended the Data Access Application
Block, you can use the same techniques and adapt the chapter’s templates and
checklists to test your own work.
Requirements for the Data Access Application Block
The Data Access Application Block has the following requirements:
●
●
●
●
●
●
●
●
The application block should support common data access operations.
The application block should be extensible.
The application block should manage database connections.
The application block should provide a straightforward way to handle parameters
for stored procedures.
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 have good performance metrics.
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 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 Data Access Application Block’s
design must satisfy.