[andrcuns]

Context

Add preconditions and expected results to Rust test results, matching the support added in allure-ruby. Test authors can document what must be true before a test runs and what outcome it is intended to produce, separately from the test description.

Both fields support independent Markdown and HTML values:

• precondition and preconditionHtml
• expectedResult and expectedResultHtml

Set them before execution using TestOptions builders:

TestOptions::new("dashboard")
    .with_precondition("User is logged in")
    .with_expected_result("Dashboard is displayed")

Or update them while a test is running using the thread-bound runtime helpers:

allure_rust_commons::precondition("User is logged in");
allure_rust_commons::expected_result("Dashboard is displayed");

HTML variants are available through with_precondition_html / with_expected_result_html builders and precondition_html / expected_result_html runtime helpers. Adapters can also set the fields through AllureFacade methods or low-level lifecycle parameters.

These values are report metadata only: they do not perform setup or assert the test outcome.

Checklist

• Sign Allure CLA
• Provide unit tests

[github-actions]

Allure Report Summary

	Environment	Duration	Stats	New	Flaky	Retry
	All tests	20m 49s	⁠ 248	6	0	0
	ubuntu-latest-rust-stable	10m 50s	⁠ 124	3	0	0
	windows-latest-rust-stable	9m 58s	⁠ 124	3	0	0

Reports: Awesome

Context: de96e01e, CI

Allure TestOps: Allure Rust GitHub actions run (2026-11-02T17:13:10.364Z)

Artifacts used (6)

• allure-results-smoke-nextest-ubuntu-latest-rust-stable.zip
• allure-results-smoke-nextest-windows-latest-rust-stable.zip
• allure-results-smoke-ubuntu-latest-rust-stable.zip
• allure-results-smoke-windows-latest-rust-stable.zip
• allure-results-ubuntu-latest-rust-stable.zip
• allure-results-windows-latest-rust-stable.zip