You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to Serenity version 4.1.0, I noticed an issue where the test count in the Serenity report is incorrect when using parallel execution at the scenario level.
By default, parallel execution at the feature level works fine, and the test count in the report is accurate. However, when switching to parallel execution at the scenario level with a Cucumber runner, the test count becomes inconsistent with the actual number of executed scenarios.
This issue persists across all 4.x versions I have tested.
The text was updated successfully, but these errors were encountered:
After upgrading to Serenity version 4.1.0, I noticed an issue where the test count in the Serenity report is incorrect when using parallel execution at the scenario level.
By default, parallel execution at the feature level works fine, and the test count in the report is accurate. However, when switching to parallel execution at the scenario level with a Cucumber runner, the test count becomes inconsistent with the actual number of executed scenarios.
This issue persists across all 4.x versions I have tested.
The text was updated successfully, but these errors were encountered: