Allure steps not marked as failed when using SoftAssertions inside static steps

[lubomsky]

Description

When using SoftAssertions inside Allure steps, the steps are not properly marked as failed in the Allure report, even when the assertions fail.

Steps to reproduce

1. Create a test class with the following code:

import io.qameta.allure.Allure
import io.qameta.allure.Description
import io.qameta.allure.Feature
import org.assertj.core.api.Assertions.assertThat
import org.assertj.core.api.SoftAssertions
import org.junit.jupiter.api.DisplayName
import org.junit.jupiter.api.Test

@Feature("Allure step behaviour with soft assertions")
class Tests {

    @Test
    @DisplayName("SoftAssertions execution with static step inside")
    @Description("Check if SoftAssertions mark steps as failed")
    fun checkAllureWithSoftAssertionsStaticStepInside() {
        val softly = SoftAssertions()

        softly.check { Allure.step("Sample boolean check") { -> assertThat(false).isTrue } }
        softly.check { Allure.step("Sample String check") { -> assertThat("xyz").isEqualTo("abc") } }

        softly.assertAll()
    }

    @Test
    @DisplayName("SoftAssertions execution with static step outside")
    @Description("Check if SoftAssertions mark steps as failed")
    fun checkAllureWithSoftAssertionsStaticStepOutside() {
        val softly = SoftAssertions()

        Allure.step("Sample boolean check") { -> softly.assertThat(false).isTrue }
        Allure.step("Sample String check") { -> softly.assertThat("xyz").isEqualTo("abc") }

        softly.assertAll()
    }
}

2. Execute the tests.
3. Generate the report.

Expected Behavior

The first test should correctly register steps as failed based on the assertions.
The second test should also register steps as failed.

Actual Behavior

In the first test, steps reflect their correct status (failed).
In the second test, all steps are reported as passed, regardless of assertion outcomes.

Screenshots

Result of the second test

**Result of the first test **