Description

a-zorina

opened on Jul 10, 2026

Issue body actions

What happened?

When a WebDriver decorated with AllureWebDriverBiDi is closed via driver.quit() inside a JUnit 5 @AfterEach, the resulting "WebDriver BiDi network"/"WebDriver BiDi log" attachments are written to the tearDown fixture container instead of the test result itself.

What Allure Integration are you using?

allure-selenium-bidi

What version of Allure Integration you are using?

3.0-SNAPSHOT, commit 22cb102

What version of Allure Report you are using?

3.14.0

Code of Conduct

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

Activity

1. a-zorina

   added

   pr:bugSomething isn't workingSomething isn't working

   triage

   on Jul 10, 2026
2. baev

   removed

   pr:bugSomething isn't workingSomething isn't working

   on Jul 10, 2026
3. baev

   added the

   Bug

   issue type on Jul 10, 2026
4. baev commented on Jul 10, 2026

   

   baev

   on Jul 10, 2026

   Member

   More actions

   @a-zorina, why do you think this is a bug? Logs are flushed when the session closes. If driver.quit() is called in AfterEach, the attachments will also be added to AfterEach.
5. baev

   removed

   triage

   on Jul 10, 2026
6. a-zorina commented on Jul 10, 2026

   

   a-zorina

   on Jul 10, 2026

   Author

   More actions

   driver.quit() in AfterEach is a standard tear down pattern in selenium docs: https://www.selenium.dev/documentation/webdriver/getting_started/using_selenium/, so I'm assuming that's how these tests are usually written.
   And the resulting placement of the attachments in the actual report looks awkward.

Issue actions