-
Notifications
You must be signed in to change notification settings - Fork 61
Full-page Chrome screenshots using ShutterBug in conjunction with Xebium #168
Comments
You can pass the web driver in My Solution: method
in
Lastly,
|
I greatly appreciate your help Ismail. Some questions:
Thanks again! |
|
We need to support Chrome as well as Firefox and have run into the issue wherein Chrome, being W3C compliant in this area, takes screenshot of the top-level browsing context’s viewport only. Full-page screenshots are an absolute requirement for us.
The most viable solution we’ve uncovered is to use the well-regarded ShutterBug (https://github.com/assertthat/selenium-shutterbug) for this purpose (if you know of an easier/better approach, please let me know!).
It appears that the best way for us to use ShutterBug with FitNesse is to create a fixture for that purpose. Ironically, although we are a Java shop (and I personally spend most of my time architecting/writing java code), we have never written a fixture because our automated testing group exclusively uses FitNesse/Xebium/Selenium stack—though we make extensive use of Javascript via
runScript
andstoreEval
commands. Thus, fixtures are new territory for me.In this post (http://disq.us/p/1kg9diy), the ShutterBug author suggests:
I don’t see how we could pass WebDriver instance to ShutterBug fixture via Xebium WebDriver supplier (
DefaultWebDriverSupplier
). Is it possible, or would we be better off taking the approach of jguglielmi in the OASIS project and incorporating the XebiumDefaultWebDriverSupplier
code into our own?Some guidance would be greatly appreciated!
The text was updated successfully, but these errors were encountered: