Martin Sefcik

It looks like it is happening because of missing child (container -> result) reference in test container json file. I was able to get it working correctly by modifying `io.qameta.allure.junitplatform.AllureJunitPlatform#stopTestContainer`...

It is randomly happing also to us and it is really annoying. Sometimes it fails , sometimes it passes with the same response body. I spend a lot of time...

@tolbala Thank you for workaround. Could you also provide implementation for `attachLogs()`, `getRequestLog()` and `getResponseLog()` methods ?

I still think it's a bug in Allure. In JUnit5 in case of parametrized test `DisplayName` is meant as name of test for all parametrized cases and `ParameterizedTest.name` is meant...

@abayer Any updates on this? When can we expect this will be completed and merged? As it is very missing feature in declarative pipeline.

@mmcdermo2 for us it was also failing on libericaJDK 17

Guys you mentioned webvirtcloud a year ago, but webvirtclound was pushed to the repository just few days ago (see https://github.com/retspen/webvirtcloud) So I'm confused, and also confused what's the difference between...

@pavelicii Which JDK distribution? Liberica?

@korpus95 I didn't solve the problem, I just proposed what needs to be changed in allure-java library to fix it.

> To set a default environment go to: `Collection Settings > Presets > Environment` and pick an environment in the dropdown. I would expect that it will be configurable in...