-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug?] Screenshot is not added in generated allure reported #1131
Comments
I have the same problem |
very annoying |
I also see this. It also seems to attach screenshots so the last "step" (eg: |
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? |
1 similar comment
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 |
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):
The text was updated successfully, but these errors were encountered: