★ wanayoo — archive 1999 https://github.com/allure-framework/allure-java/pull/440Nouvelle recherche | Portail wanayoo
Skip to content
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

Reuse Selenide screenshots #440

Open
wants to merge 2 commits into
base: master
from

Conversation

@dstekanov
Copy link
Contributor

@dstekanov dstekanov commented Apr 25, 2020

Context

The idea behind it is to not take screenshot 2 times (by Selenide and by Allure) but check if Selenide has already taken one and re-use it otherwise take a new screenshot.

Selenide issue history selenide/selenide#1002

Checklist

dstekanov added 2 commits Apr 25, 2020
@@ -91,10 +95,24 @@ public AllureSelenide disableLogs(final LogType logType) {
}

private static Optional<byte[]> getScreenshotBytes() {
return ScreenShotLaboratory.getInstance().getLastThreadScreenshot()

This comment has been minimized.

@baev

baev Jun 5, 2020
Member

what if you are using saveScreenshots=true and make a single screenshot manually at test start? It seems like you'll get the same screenshot in all the steps

This comment has been minimized.

@dstekanov

dstekanov Jun 16, 2020
Author Contributor

If I understand correctly, it should not be a case because Selenide will take a separate screenshot on each fail

This comment has been minimized.

@SeleniumTestAB

SeleniumTestAB Jul 11, 2020

@dstekanov and what if we got a case, when someone manually produces a screenshot on fail to attach it to the Main Test Result Page and not under the steps, while also wanting that screenshot to be under given step? Also what if we use Junit assertAll with selenide boolean methods?

Copy link
Contributor

@lasnamae lasnamae left a comment

Sorry, it was just a test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.