Skip to content

Add Success Rate and Issues columns to suites CSV export (fixes #3092, fixes #2727) - #3501

Closed
siri1410 wants to merge 1 commit into
allure-framework:mainfrom
siri1410:suites-csv-success-rate-and-links
Closed

siri1410 wants to merge 1 commit into
allure-framework:mainfrom
siri1410:suites-csv-success-rate-and-links

Conversation

@siri1410

Copy link
Copy Markdown

fixes #3092, fixes #2727

Context

Adds two columns to the Suites tab Download CSV export (data/suites.csv):

  • Success Rate (Add Success Rate Column to Suite Tab CSV Export #3092): the same value shown in the test result's History tab, i.e. passed / total of the history statistic, floored to two decimals (e.g. 66.66%, 100%). The value is read from the history extra block that HistoryPlugin attaches before SuitesPlugin runs. When a test has no history yet (first run, or no history/ folder copied into results), the cell is empty, the same as the History tab.
  • Issues (Issues in csv file #2727): the result's links of type issue, exported as name (url) and separated by , . For example, allure.issue("https://example.atlassian.net/browse/ABC-1", "ABC-1") becomes ABC-1 (https://example.atlassian.net/browse/ABC-1). A link with only a name or only a URL is exported as that value.

Implementation notes:

  • CsvExportSuite (plugin API) gets a new CsvExportSuite(TestResult, Statistic) constructor. The existing CsvExportSuite(TestResult) constructor is kept for external plugins and leaves Success Rate empty.
  • HistoryPlugin.HISTORY_BLOCK_NAME is now public, like ExecutorPlugin.EXECUTORS_BLOCK_NAME, so SuitesPlugin can read the history block.

Checklist

…e-framework#3092, fixes allure-framework#2727)

- Success Rate is taken from the test result history statistic and uses
  the same calculation as the history tab (passed / total, floored to two
  decimals). It is empty when the test has no history.
- Issues lists the issue links of the test result as "name (url)".
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@CLAassistant

CLAassistant commented Sep 23, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@siri1410 siri1410 closed this Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Success Rate Column to Suite Tab CSV Export Issues in csv file

2 participants