Brief description of the problem:
I started using the allure-awaitility library and saw strange behavior - after the first call to the await() function in the test, either the hierarchy of steps in the report breaks or there are no steps at all after the step that contains await()
Steps to reproduce:
I created a simple project to demonstrate the problem (Kotlin + TestNG): https://github.com/petrschitow/allure-awaitility-issue
To reproduce the error, you need to run the tests and generate an allure-report using the following commands:
mvn clean test
allure serve target/allure-results
To observe different behavior, run tests with commented/uncommented lines 32-34 in TestConfiguration.kt file
You can find screenshots with actual/expected behaviour here
P.S. The pet-api is unstable, so you may need to run the test a couple of times.
Brief description of the problem:
I started using the allure-awaitility library and saw strange behavior - after the first call to the await() function in the test, either the hierarchy of steps in the report breaks or there are no steps at all after the step that contains await()
Steps to reproduce:
I created a simple project to demonstrate the problem (Kotlin + TestNG): https://github.com/petrschitow/allure-awaitility-issue
To reproduce the error, you need to run the tests and generate an allure-report using the following commands:
mvn clean testallure serve target/allure-resultsTo observe different behavior, run tests with commented/uncommented lines 32-34 in TestConfiguration.kt file
You can find screenshots with actual/expected behaviour here
P.S. The pet-api is unstable, so you may need to run the test a couple of times.