[andrcuns]

Context

Breaking change

Makes full_name field correct uniq representation of a test case (was not taking in to account file name before). When used with testops, the test cases will be regenerated and not match ones created from previous runs due to added file path in the unique name identifier

Muted tests

Support the mutedTests list in Allure test plans so muted RSpec examples and Cucumber scenarios are skipped instead of affecting the test run outcome.

• Read muted test-case IDs or selectors from testplan.json and ignore missing fields in test-plan entries.
• Skip matching RSpec examples through :skip metadata and Cucumber scenarios through the public Around hook DSL.
• Report matching tests as skipped with statusDetails.muted = true. Muted test bodies are not executed.

Example

Example with executing a test plan with some tests muted using this repository tests as example:

❯ brake test
Executing test for allure-ruby-commons
Run options: include {rerun_file_path: #<Proc: /home/agent/.herdr/worktrees/allure-ruby/test-plan-muted/allure-rspec/lib/allure_rspec/_utils.rb:9>}

Allure::ResultUtils
  returns framework label (PENDING: Skipped by Allure test plan)
  returns epic label
  returns feature label

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) Allure::ResultUtils returns framework label
     # Skipped by Allure test plan
     # ./spec/unit/result_utils_spec.rb:15


Finished in 0.00263 seconds (files took 0.12163 seconds to load)
3 examples, 0 failures, 1 pending

Executing test for allure-cucumber
Run options: include {rerun_file_path: #<Proc: /home/agent/.herdr/worktrees/allure-ruby/test-plan-muted/allure-rspec/lib/allure_rspec/_utils.rb:9>}

AllureCucumber
  returns cucumber configuration (PENDING: Skipped by Allure test plan)
  yields cucumber configuration
  supports common configuration options

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) AllureCucumber returns cucumber configuration
     # Skipped by Allure test plan
     # ./spec/unit/allure_cucumber_spec.rb:11


Finished in 0.00506 seconds (files took 0.19623 seconds to load)
3 examples, 0 failures, 1 pending

Executing test for allure-rspec
Run options: include {rerun_file_path: #<Proc: ./lib/allure_rspec/_utils.rb:9>}

AllureRspec
  returns rspec configuration (PENDING: Skipped by Allure test plan)
  yields rspec configuration
  supports common configuration options

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) AllureRspec returns rspec configuration
     # Skipped by Allure test plan
     # ./spec/unit/allure_rspec_spec.rb:11


Finished in 0.00651 seconds (files took 0.10993 seconds to load)
3 examples, 0 failures, 1 pending

Checklist

• Sign Allure CLA
• Provide unit tests

[github-actions]

Allure Report Summary

	Environment	Duration	Stats	New	Flaky	Retry
	All tests	4s	⁠ 1260	1260	0	0
	ubuntu-ruby-3_3-oj-false	779ms	⁠ 210	210	0	0
	ubuntu-ruby-3_3-oj-true	512ms	⁠ 210	210	0	0
	ubuntu-ruby-3_4-oj-false	878ms	⁠ 210	210	0	0
	ubuntu-ruby-3_4-oj-true	678ms	⁠ 210	210	0	0
	ubuntu-ruby-4_0-oj-false	725ms	⁠ 210	210	0	0
	ubuntu-ruby-4_0-oj-true	767ms	⁠ 210	210	0	0

Allure TestOps: Allure Ruby GitHub actions run (2026-11-06T16:05:49.851Z)

Artifacts used (6)

• allure-results-test-ruby-3.3-oj-false.zip
• allure-results-test-ruby-3.3-oj-true.zip
• allure-results-test-ruby-3.4-oj-false.zip
• allure-results-test-ruby-3.4-oj-true.zip
• allure-results-test-ruby-4.0-oj-false.zip
• allure-results-test-ruby-4.0-oj-true.zip

[andrcuns]

@epszaw This is kind of a preemptive support for muted tests skip. Used ruby first as I'm more familiar so easier to test ideas out