Summary

Quality Gates configured in allurerc.json do not appear to be evaluated when generating an Allure 3 report using the CLI.

Environment
Allure CLI: 3.14.3
Java: 21
Test framework: TestNG
Build tool: Gradle
CI: Jenkins
Operating System: Windows
Configuration

The report is generated using:

allure generate --config allurerc.json allure-results -o allure-report --clean

The report is then opened with:

allure open allure-report

Example qualityGate configuration tested:

"qualityGate": {
  "rules": [
    {
      "id": "success-rate-95",
      "successRate": 0.95
    }
  ]
}

The same behavior is observed with other configurations, including:

maxFailures: 0
maxFailures: 1
successRate: 1.0
fastFail: true
Steps to Reproduce
Execute a TestNG test suite that produces one or more failed tests.

Generate the Allure report using:

allure generate allure-results; allure open
Configure a Quality Gate that should clearly fail (for example maxFailures: 0 or successRate: 1.0).
Observe the CLI exit code and generated report.
Expected Behavior

The configured Quality Gate should be evaluated during report generation. If the configured rule is not satisfied, the CLI should fail (non-zero exit code) or otherwise indicate that the Quality Gate has failed.

Actual Behavior

The report is generated successfully regardless of the configured Quality Gate. The configured rules do not appear to affect the generation process, even when the execution results clearly violate the configured thresholds.

Additional Notes
The allurerc.json file is passed explicitly using the --config option.
Multiple Quality Gate configurations have been tested with the same result.
The generated report itself appears to be correct; only the Quality Gate evaluation seems to be ignored.
This behavior is reproducible in a Java + TestNG + Gradle project running in Jenkins.