Doubts about "think time" interpretations
Hi everybody, we have a question regarding the correct interpretation of the think time in the reports we are receiving after the end of a LoadNinja testing session. We performed a test in order to...
Forum Discussion
Hi, thanks for the kind answer.
Your answer seems reasonable, but could you please confirm us that the "think time" duration is not influenced by the page loading time?
In other words: the time that a virtual user waits for the page to load is not included in the think time reported in final statistic summary?
Thanks in advance
Hi fdelmoro
From a rendering point of view it woudnt.
But it does affect how long a UI test executes.
To save confusion and doubts we provide think time values in the reports.
https://support.smartbear.com/loadninja/docs/results/navigation-timings.html
Kind Regards
Vinnie
Hello, we got this feedback from the LoadNinja customer care:
"This corresponds to the definition of the “Think time” metric - the average time virtual users spent simulating pauses between user actions during the playback. Anyway, I think that using the “Think time” metric is not the right way to measure if page load times are within the expected boundaries. My recommendation would be to use SLA validations instead – they will be throwing errors if a step takes longer than expected and you’ll have an opportunity to measure the number of such errors".
This answer seems to agree with us that "Think time” metric is not the right way to measure page load times performances", but it suggests to use the threshold SLA validation.
From our direct experience the SLA threshold validation takes into account the think time, can you please confirm this hypotesis?
If this is true, do you confirm the answer given above? (they suggested not to use think time as relevant metric but suggest a threshold validation that takes into account the think time)
