What really impacts the user experience is transaction time
In many cases, individual response time (per request) and average response time across all http requests are not very meaningful. What really impacts the user experience is the transaction time. Usually, this corresponds to the time spent loading a web page, i.e. a group of requests, or a group of logical steps that corresponds to a user click, or an end-to-end sequence. For example a transaction could be:
Login -> Browse Data -> Download report
Nouvola is excited to introduce Transactions and Transaction Timing.
With this new set of capabilities you can group a set of requests (or a sub-session) into a transaction, and then see transaction aggregated results, and report metrics on end-to end workflows. Once created, you can reuse your transactionslike lego blocks and build different tests and sessions. For example, you can create an authentication transaction that is appended at the beginning of multiple tests.
How to do it? Use either Nouvola DiveTrace or Nouvola DiveProxy or Import your sessions, one click or one page at a time. Save the resulting sessions, then combine them sequentially in complex sequences, or re-use some of them to create different sequences. It just takes a few clicks to build the sequence you like.
In addition, when you create the test, you can now define think time per page or per each individual request. And when you look at the results, you can see aggregated results per transaction, not just individual requests. In this way you can easily identify transactions with higher response times, errors or performance issues.
Interested in the details? Go here for a step-by-step breakdown of exactly how it works:
We'd love your feedback! Email us to share your thoughts on this new feature.
The Nouvola Team