Repository navigation
馃悶: Selenium BiDi attachments land in the tearDown fixture, not the test result聽#1322
Description
Activity
driver.quit()inAfterEachis 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.
What happened?
When a WebDriver decorated with
AllureWebDriverBiDiis closed viadriver.quit()inside a JUnit 5@AfterEach, the resulting "WebDriver BiDi network"/"WebDriver BiDi log" attachments are written to thetearDownfixture 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