[andrcuns]

Context

Java 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.

Use the new runtime helpers to provide Markdown content:

Allure.precondition("User is **logged in**");
Allure.expectedResult("**Dashboard** is displayed");

Use explicit HTML when rich formatting is needed:

Allure.preconditionHtml("<p>User is logged in</p>");
Allure.expectedResultHtml("<p>Dashboard is displayed</p>");

These helpers work like Java's description helpers:

• Calls inside a test update that test.
• Calls inside a before fixture provide defaults for tests linked to that fixture's scope.
• Explicit test values, including empty strings, take precedence over scope defaults independently for each field.
• Markdown and HTML values are stored separately; HTML takes precedence when rendered in a supporting report.

The fields are written to test results as precondition, preconditionHtml, expectedResult, and expectedResultHtml. Custom integrations can also set them through the model's fluent accessors. Existing tests need no changes.

This brings Java support in line with the Ruby integration, while following Java's shared-setup metadata conventions. In Allure 3 Awesome reports, the corresponding report support displays 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	23m 56s	⁠ 1817 ⁠ 2 ⁠ 1	104	0	0
	ubuntu-jdk-17	8m 48s	⁠ 885 ⁠ 1 ⁠ 1	52	0	0
	ubuntu-jdk-25	15m 8s	⁠ 932 ⁠ 1	52	0	0

Reports: Awesome

Context: 9086f5ea, Build

Allure TestOps: Allure Java GitHub actions run (2026-11-03T16:18:15.080Z)

Artifacts used (2)

• allure-results-test-jdk-17.zip
• allure-results-test-jdk-25.zip