In the real world, users login at the beginning of their day, conduct multiple operations throughout the day, then logout at the end of their day. What is the best way to construct a test plan that emulates this typical user behavior?
ScenarioBuilder has automatic response time reporting at the Scenario and Component levels. To isolate and report on specific events within these levels, simply tag a step or series of steps with Begin and End “Transaction” Actions. ScenarioBuilder will include Transaction response times in all reports and graphs.
To meet the challenge outlined above, we’ll start by creating a Scenario that loads the Windows Live web application;
Now, thinking like a real user, let’s add a step that finds an image that loads with the application. This will ensure that the page has loaded before any further steps are taken by the Scenario. We’ll capture the the “Windows Live” logo at the top of the screen;
Last, we’ll add a Transaction to measure the time it takes for the webpage to load. Notice where we’ve placed the Begin and End “Transaction” Actions in the Scenario;
By framing the “Find Image” Action, our Transaction will measure only the amount of time taken from the click of the “Log In” button to the loading of the web page. The “Execution Report” provides the response time for the overall Scenario plus the “LoadWebPage” Transaction;
In our example, the web page loaded in under three seconds. However, the true test will come through load testing where AppLoader can take the Scenario and use it to impose hundreds, or even thousands of concurrent users on the application;
So remember to use Transactions for that extra layer of reporting so you can get to the bottom of your performance issues.