What happened?

When using allure-awaitility, steps executed after the first Awaitility in a test do not appear in the report.
Example for reproduction: https://github.com/zakrzhevskiy-as/allure-awaitility-bug

Prerequisites:

• Initialize the default condition evaluation listener for Awaitility

Reproduction:

1. A step is executed in the test using Allure.step("name", { })
2. The first Awaitility is called
3. The second Awaitility is called
4. A step is executed in the test using Allure.step("name2", { })

Expected result:

• All steps in the test body are displayed in the report:
  1. name
  2. first Awaitility
  3. second Awaitility
  4. name2

Actual result:

• When creating a step after an Awaitility has been executed, io.qameta.allure.AllureLifecycle#threadContext considers the UUID of the current step to be the UUID of the first Awaitility step, but not the key of the TestResult, stored in the io.qameta.allure.AllureLifecycle#storage

What Allure Integration are you using?

allure-awaitility

What version of Allure Integration you are using?

2.29.0

What version of Allure Report you are using?

2.29.0

Code of Conduct

• I agree to follow this project's Code of Conduct