[andrcuns]

Context

Ruby tests can now report preconditions and expected results separately from the test description. This makes it easier to explain what must be true before a test runs and what a successful outcome should look like, without combining everything into one description.

Adds support for precondition, preconditionHtml, expectedResult, and expectedResultHtml in test results, with helpers that work like the existing description helpers:

Allure.add_precondition("User is logged in")
Allure.add_expected_result("Dashboard is displayed")

# Use explicit HTML when rich formatting is needed.
Allure.precondition_html("<p>User is logged in</p>")
Allure.expected_result_html("<p>Dashboard is displayed</p>")

These fields complement the existing description and support Markdown or explicit HTML, just like descriptions. The corresponding Allure 3 report support was added in allure-framework/allure3#1189: Awesome reports display Precondition before test execution and Expected result after teardown.

Checklist

• Sign Allure CLA
• Provide unit tests

[github-actions]

Allure Report Summary

	Environment	Duration	Stats	New	Flaky	Retry
	All tests	3s	⁠ 1158	1158	0	0
	ubuntu-ruby-3_3-oj-false	585ms	⁠ 193	193	0	0
	ubuntu-ruby-3_3-oj-true	498ms	⁠ 193	193	0	0
	ubuntu-ruby-3_4-oj-false	711ms	⁠ 193	193	0	0
	ubuntu-ruby-3_4-oj-true	346ms	⁠ 193	193	0	0
	ubuntu-ruby-4_0-oj-false	384ms	⁠ 193	193	0	0
	ubuntu-ruby-4_0-oj-true	655ms	⁠ 193	193	0	0

Allure TestOps: Allure Ruby GitHub actions run (2026-10-29T08:55:51.205Z)

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

[formaceft-93]

🔥