Skip to content

Allure Dashboard overview shows incorrect testcase count with Pabot Robot Framework runs #897

@PreethiSiran

Description

@PreethiSiran

Describe the Bug

When running Robot Framework tests for multiple websites in parallel using Pabot (with argument files), the Allure Dashboard overview displays only the testcase count for a single URL instead of the total count across all URLs. For example, with 11 testcases per URL and 2 URLs, the timeline correctly shows 22 testcases, but the overview only shows 11.

Steps to Reproduce

  1. Run Robot Framework tests in parallel using Pabot with argument files for multiple URLs:
    pabot --listener "allure_robotframework;allure-results" --argumentfile1 arg1.txt --argumentfile2 arg2.txt tests/Global
  2. Open the generated Allure report.
  3. Observe the timeline tab: it shows the correct total testcase count (e.g., 22).
  4. Observe the overview tab: it only shows the testcase count for a single URL (e.g., 11), not the total.

Expected Behaviour

  • The Dashboard overview should display the total number of executed testcases from all parallel runs (i.e., sum across all URLs/sites), matching the count shown in the timeline.
  • The pass/fail count should display the total number (sum of pass/fail across all URLs).

Screenshots or Additional Context

Allure Dashboard - Overview Tab showing only 11 testcase of single url
Image

Allure Dashboard - Timeline Tab showing total 22 testcase of two urls
Image

Environment:

  • Allure Commandline version: 2.34.1
  • Allure RobotFramework listener version: 2.15.0
  • Robot Framework version: 6.1.1
  • Pabot version: 4.1.1
  • OS: Windows
  • Browser: Chrome
  • Java version: 24.0.2

What Language are you using?

Python (RobotFramework)

What Framework/Allure Integration you are using?

allure-robotframework

What version of Allure Integration you are using?

2.15.0

What version of Allure Report you are using?

2.34.1

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:bugPull requests that fix bugs

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions