Enterprise Library Test Guide - Willy .Net

Introduction
This section provides an overview of functional testing as it was used with the Enterprise
Library. To see how a specific application block or the Enterprise Library Core
was tested, refer to the relevant chapter. In general, there are four steps to functional
testing:
1. Create the test cases for the design and the code.
2. Perform design reviews to verify that the design addresses all functional requirements.
3. Perform code reviews to verify that the code addresses all functional requirements.
4. Perform automated tests to validate that the application is functioning as it
should and to simulate situations such as multiple users concurrently using the
application.
Creating Test Cases
Design test cases specify the requirements that a design must fulfill for the application
to perform the way it is expected to. Each test case should be satisfied by a
specific part of the design. For example, if the application is meant to be extensible,
there must be a specific way that the application can be extended, such as an interface
or a base class.
When you write the design test cases, have a list of requirements and any designrelated
documents, such as architectural diagrams and class diagrams, available so
you can incorporate this information into the test cases. The Microsoft test teams
found it helpful to create tables that listed each design requirement and its priority.
Table 1 is an example of some of the design cases for the Cryptography Application
Block.
Table 1: Cryptography Application Block Design Test Cases
Priority
High
High
High
Design Test Case
Verify that the symmetric algorithm providers and the hash providers are extensible.
Verify that there is a consistent approach to creating symmetric algorithm providers
and hash providers.
Verify that there is a facade that mediates between the client code and the
application block’s cryptographic functions such as encryption, decryption, and
hashing.