-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Serenity.takeScreenshot + GEB not working #941
Comments
GEB is not officially integrated with Serenity (as in, there are no integration tests or specific code around it), so I couldn't really say. |
But using Selenium 2.5.3 with Serenity 1.5.x (which is built against Selenium 3) might not help things... |
Thank you so far for your fast reply. I could get it to work in the end. I just had to
I combined those needs in the GebConfig.groovy as follows:
Now my GEB-Tests and Serenity-reports (including screenshots) are working properly, as far as i can say. |
Hi @tde-desc , |
Hi @alexfch , exactly, i was using the setup you are looking for successfully in multiple projects in a productive environment. Unfortunately I'm not having access on those projects anymore so I can just try to reproduce what i did so far to accomplish that setup:
I hope this is going to help you. Feel free to ask if any further information is required. |
Hi @tde-desc , Thank you very much for your help! I was able to set the project up and it's successfully running! |
As it seems like Serenity is not being supported in conjunction with GEB natively. I can get it to work easiliy though and its integrating quite well, having the following setup:
Unfortunately Serentiy is not generating screenshots, neither by default nor when I'm calling Serenity#takeScreenshot. It seems like WebDriverFacade.proxiedWebDriver is never being instantiated as it's always null, just like in this issue, which leads to BaseStepListener#shouldTakeScreenshots always returning false. I'm somehow afraid GEB is creating its own driver which Serenity is not being aware of...
Any idea?
The text was updated successfully, but these errors were encountered: