Create and analyze your end-to-end transactions page by page (or anyway you like)

Posted by on October 12, 2016 9:17pm
In many cases, individual response time (per http request) and average response time across all the http requests are not very meaningful.

What is really impactful to the user experience is the transaction time. 

So when looking at performance testing results, the really important metric is the end-to-end transaction time. Usually, this corresponds to a web page load time, i.e. a group of requests, or a group of logical steps that corresponds to a user click. 


Therefore, when creating complex test scenarios, it is often important to be able to group multiple requests into logical steps which become separate entities. So when a single click generates dozens of requests, all these requests can be grouped together in a transaction, and mapped to a single page. 

The additional advantage of ‘per-click transactions‘ is that those logical components can be reused as building blocks across multiple tests and different scenarios. Some examples are authentication, shopping cart checkout, downloading a report, posting a review, etc⬦

TransactionsResults.pngFor example you might want to know how long it takes for the authentication handshake to complete. In this case the authentication sequence can be considered as a logical step, i.e. a transaction.  So, when the time comes to analyze the whole transaction, it is easy to see how long it took for the authentication step, and how long it took for everything else.

In addition, since web pages have often incorporate several requests, it is useful to know how the requests map into each page. So you can see which specific pages present performance issues and/or which are the fastest.

Sometimes it is not just a single page or step, but a sequence of pages or clicks, in which case you can group the sequence together to define a logical transaction in the overall scenario being tested. For example, one might be interested in the sequence:

 Login -> Browse Reports -> Download Reports.


Search -> Browse Products -> Select Product -> Add to Cart

Nouvola provides an innovative disruptive solution for advanced performance scenarios like the ones described above. With its new set of capabilities, Transactions and Transaction Timing, Nouvlla provides a UI-based, modular solution, where individual steps can be separated logically and combined to build longer and more complex transactions. On the results side, you’ll be able to look at the results both as a complete transaction and step-by-step. In Nouvola DiveCloud terminology, a transaction is just another type of session.

In DiveCloud, it is possible to save each transaction separately and then combine them together by using the Multi-Session capability. When recording via DiveTrace, each click or logical step can be saved separately. Then transactions can be combined to build complex scenarios as easily as playing with legos. And if there are data that need to be passed or shared, this will be automatically done.

The same transaction can also be used to build a different scenario. For example, the authentication transaction, once created, can be applied to any scenario that requires it.

And when results are ready, each single transaction can be analyzed separately and/or viewed together in the Overview tab. So you can look at results per page, per click, or per transaction.  And you can drill even deeper and analyze individual requests, or take a global view and see the overall performance, start to finish.

Want to give it a try? Request a free trial below.

Learn more