As stated above, we are using the load test project that comes
in Visual Studio Team Suite. If you have the Visual Studio Team System Test
edition, this should include all testing projects as well. This article is not
a tutorial for using the Visual Studio test projects, we assume familiarity
The first load test (NonCached.loadtest) consists of the
non-cached reporting web pages that will be displayed multiple times. Figure 1
shows what the load test looks like, including scenarios. Both load tests have
the same scenario setup.
Figure 1: Non Cached load test
Scenario 1 is the only scenario used to keep this simple. We
use two web tests, the CustomerNonCached web test and the AllNonCached web
test. The CustomerNonCached web test displays the "CompanySales.rpt"
report, which displays the orders by customer. The test displays the first page
of the report then pages through multiple pages of this report. The web page is
the default.aspx web page which has a Crystal Report Viewer on it bound to
The AllNonCached web test displays all three reports,
including CompanySales.rpt, SalesOrders.rpt, and SalesPerson.rpt. AllNonCahced
first displays default.aspx page (CompanySales.rpt is bound to that Crystal
Viewer) and pages through the report.
Then the test displays SalesOrders.aspx which has a crystal
report viewer bound to the SalesOrders.rpt report. This just displays once,
because SalesOrders.rpt is a one page report. Then SalesPerson.aspx is
displayed, which, once again, is a Crystal report viewer bound to the report
SalesPerson.rpt. Pretty simple stuff I will admit.
The test pages through the report one page at a time and
also navigates to the end of the report. The test then displays default.aspx
again and navigates across a couple of pages of the report. The test then
navigates back to Salesperson.aspx and displays a few more pages before ending.
That shows what is going on in the AllNonCached tests. The NonCached.loadtest
runs the CustomerNonCached.webtest 35% of the testing time, and AllNonCached.webtest
65% of the time. This test also distributes the browsers running the test between
IE 7.0 and Firefox 2.0. I set IE up at 84% and Firefox at 16%. Again this was
to keep the tests relatively simple.
Finally, the network mix is set up to use a variety of
connection speeds. For this test I assume that all users will have a minimum of
cable/DSL speeds. So then 16% of the mix are LAN connections, with 58%
cable/DSL of 1.5 Mbps, and 26% Cable/DSL of 384 mbps. This test assumes the
reports are for external customers for the most part rather than internal