Enterprise Library Test Guide - Willy .Net

196
Enterprise Library Test Guide
ID Scenario Transaction Users
5 Use ExecuteNonQuery to With/Without 1, 10, 50, 150,
retrieve output parameters. Transaction 300
6 Use a DataSet to update the
database.
7 Add a new DataTable to the
existing DataSet.
8 Retrieve multiple rows as
XML
With/Without
Transaction
With/Without
Transaction
With/Without
Transaction
1, 10, 50, 150,
300
1, 10, 50, 150,
300
1, 10, 50, 150,
300
Database
provider
SQL Server
SQL Server
SQL Server
SQL Server
Creating the Test Harness
For an example of how to create a test harness, see Building Test Harnesses. Iterations
of the test should call the CreateDatabase method and create any other objects, such
as a DbCommandWrapper, that the application block uses to execute a query. For an
example of how to create a domain object for each iteration, see Using the Test Script.
Create a Web page to run the test harness.
Creating the Test Code
The test code implements the scenarios. There are two versions of the test code
shown here. The Enterprise Library uses one version and ADO.NET uses the other
version. Enterprise Library 1.1 was also used to establish a baseline. Its database
methods differ slightly from the methods in Enterprise Library–January 2006. The
Enterprise Library 1.1 code is not shown. The only scenario used for baseline comparisons
was scenario 5.
When the application block executes the scenarios within a transaction, it creates a
connection object and retrieves a transaction object. Then, the application block uses
the appropriate method overload for working with transactions.
Table 12 lists the Data Access Application Block test code.