Support composed flaky, muted, and severity annotations across Java test adapters

[baev]

Context

Allure Java now recognizes @Flaky, @Muted, and @Severity when they are composed into custom annotations, including nested compositions. These annotations work at method and class level with JUnit Platform, JUnit 4, Spock 2, and TestNG. An explicitly declared @Severity continues to take precedence over a composed value.

@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.METHOD, ElementType.TYPE})
@Flaky
@Muted
@Severity(SeverityLevel.CRITICAL)
public @interface CriticalUnstable {
}

The custom annotation can then provide consistent reporting metadata across a test suite:

@CriticalUnstable
@Test
void retriesPaymentAfterTransientFailure() {
    // ...
}

@CriticalUnstable
class ExperimentalCheckoutTests {
    // ...
}

JUnit Platform and JUnit 4 also retain flaky and muted flags when failed tests add exception details, while JUnit 4 and Spock 2 now report severity consistently with the other adapters.

Checklist

• Sign Allure CLA
• Provide unit tests

[github-actions]

Allure Report Summary

	Name	Duration	Stats	New	Flaky	Retry	Report
	Allure Java – Pull request #1331	28m 59s	2007    2	34	0	0	View
	Allure Java GitHub actions run (2026-07-21T16:44:19.188Z)	28m 59s	2007    2	34	0	0	View