Optimizing Wait Step Failures and Managing Parallel Test Runs in Virtuoso

Article Overview:

This article will cover how you can achieve the following:
Resolve issues related to step failures caused by wait times or parallel execution in Virtuoso.

Problem Statement:

What to do if you are facing an issue where a wait step fails during suite execution, but passes in individual execution, even after extending the wait limit.

Solution:

Steps may fail during suite execution due to wait time limits, even if they pass when run individually. This can happen despite extending the wait limit and may be related to parallelism or interaction settings.

To address this issue, consider making changes in the goal settings, which have proven effective in resolving step failures:

1. Goal Settings > Environment:
   • Set "Default and Maximum Parallelism" to a specific value (e.g., 10-15) instead of leaving it unlimited.
     
     
2. Goal Settings > Interaction:
   • Enable "Page Interaction Compatibility Mode." Enabling this setting ensures better compatibility with different web page interactions.

By applying these settings in the goal configuration, you should see improvements in suite execution performance, with fewer occurrences of wait step failures.

Note:

Parallelism in the context of test automation refers to the ability to execute multiple test steps or scenarios simultaneously, rather than sequentially. By running tests in parallel, you can significantly speed up execution time and increase efficiency. However, if the parallelism is not managed properly (e.g., too many steps running at once), it can overload resources or cause synchronization issues, leading to step failures. Setting a controlled limit for parallelism ensures optimal resource usage and better test stability.