Analysing slow executions in Virtuoso

About Article:

This article will describe how to analyze the slowness in the execution of tests in Virtuoso.

Problem Statement:

There are instances where the test execution in Virtuoso appears slower than expected, which might be due to various reasons.

Solution:

Usually, the slowness in Virtuoso test execution is because Virtuoso is waiting for Network Traffic before executing the next step.

This will only occur if the goal is using “Wait for Network Traffic.”

If you use Devtools around the slow steps while running the execution, you will be able to see what is happening at the time.

For example, below you can see some slow network requests.

When waiting for Network Traffic, Virtuoso will wait for a maximum of 60 seconds before performing the next step.

In these circumstances, the problem is not with the Virtuoso test but with the underlying performance of the application.

If you feel the test steps are executed successfully and still Virtuoso is waiting for the network requests, you may choose to disable - “Wait for Network Traffic.”