Enterprise Library Test Guide - Willy .Net

Using the Test Cases
This chapter discusses some of the test cases that uncovered bugs and issues in Enterprise
Library – January 2006. The test cases cover three areas:
●
●
●
Performance
Security
Functionality
For each of these test cases, there is:
●
●
●
A problem, which is the problem the test case uncovered.
A proposed solution, which is the proposed solution to the problem.
A verification, which is how the solution was tested to see whether it solved the
problem.
The test cases are representative of the sorts of bugs and issues you might see in your
own code.
Performance Testing
The goals of performance testing are:
●
●
To verify that the application block meets the performance requirements while
staying within the budgeted constraints on system resources. The performance
requirements can include different measurements, such as the time it takes to
complete a particular scenario (this is known as the response time) or the number
of concurrent or simultaneous requests that can be satisfied for a particular operation
within a specific response time. Examples of system resources are CPU time,
memory, disk I/O, and network I/O.
To identify the bottlenecks in the application block’s code. The bottlenecks can
be caused by issues such as memory leaks, slow response times, or resource
contention under load.
The performance tests measure cost in terms of system resources. The unit of measurement
is transactions per second. The baseline is the performance of Enterprise
Library version 1.1 and .NET Framework code that performs similar functions. The
cost is expressed as the percentage of overhead. This is the difference, in transactions
per second, between the baseline and Enterprise Library – January 2006, divided by
the baseline transactions per second.