[Bug?] Screenshot is not added in generated allure reported
Describe the bug
When I run my playwright tests with allure-playwright, below is allure-playwright config playwright.config.ts:
["allure-playwright",{
detail: true,
outputFolder: "./allure-results",
suiteTitle: true,
autoAttachScreenshots: true,
categories: [{
name: "Outdated tests",
messageRegex: ".FileNotFound.",
},
],
},
]
Before generate allure report, I can see the screenshot under directory: allure-results.
After I run commands "allure generate ./allure-results -o ./allure-report", and then open the allure report, I can't find any screenshot.
Expected behavior The screenshot should be added to generated allure report automatically. Is there a way to add screenshot when generate allure report after playwright running?
Desktop (please complete the following information):
- OS: Mac Pro
- Browser: Chrome
- Version: 128.0.6613.114
- Playwright Version: 1.44.0
- Allure-playwright: 3.0.0-beta.10
I have the same problem
reporter: [ ["allure-playwright", {outputFolder: "./allure-results/"}], ["line"] ], use: { trace: "retain-on-failure", headless: false, screenshot: { mode: "only-on-failure", fullPage: true, } }
It seems that the files are not saved in the right place.
Can it be fixed?
very annoying
I also see this. It also seems to attach screenshots so the last "step" (eg: test.step(() => { ... })) if a failure occurs inside one, instead of hosting the screenshot to the top level.
I am seeing this issue as well. My screenshot is under the afterHooks for playwright integration
I also have that issue, it started to occur after I updated allure-playwright to version 3.x.x, is there any workaround to fix it?
@baev
@baev
I have the same issue.
@baev do we have an ETA for this? Playwright is the most important framework so I think this is very relevant.
Is there a version I can go back to that resolves this issue? Just spent too much time today trying to figure out why I had no screenshots in my pipeline reports to stumble on this thread and realize they were there all along.
@clymerrm it works on any version before 3.x.x