[#SRC-492] captureEntirePageScreenshot - not all file paths work

Selenium Remote Control

captureEntirePageScreenshot - not all file paths work

Created: 25/Jun/08 01:19 AM Updated: 29/Sep/08 05:36 PM

Component/s:

Server

Affects Version/s:

1.0 beta 1

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	Windows

Description

« Hide

when try to call captureEntirePageScreenshot with relative path ("path\to\file.png") which exists - error is shown.
also following examples don't work:

"dir1\..\dir2\file.png"
"c:\dir1\..\dir2\file.png"
"c:/dir1/file.png"

all these paths works in captureScreenshot function, so I think, they should also work in captureEntirePageScreenshot function

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Andras Hatvani - 13/Jul/08 02:05 PM

This issue actually isn't an issue, because as it is stated on http://release.openqa.org/selenium-remote-control/0.9.2/doc/java/:
filename - the absolute path to the file to be written, e.g. "c:\blah\screenshot.png"
So this could be rather a feature request, although I don't know which use case could be the reason for it.
Furthermore, this is definitely no critical issue, as it has nothing in common with the test case execution, which is Selenium for.

[ Permlink | « Hide ]

Serik - 24/Jul/08 10:00 PM

1) you provided link to documentation of version 0.9.2, but I report problem in version 1.0 beta1 and not about captureScreenshot, but about captureEntirePageScreenshot
2) documentation about captureScreenshot is wrong, because actually it supports relative paths.
3) in documentation about captureEntirePageScreenshot I see following:
-------------
Parameters:
filename - the path to the file to persist the screenshot as. No filename extension will be appended by default. Directories will not be created if they do not exist, and an exception will be thrown, possibly by native code.
-------------
So I don't see here any mention about "absolute path"
4)use case for using capture*screenshot functions with relative path is simple: we launch several selenium servers on the same host and in several places, so we cannot use absolute paths. Also we often launch server on one host and client for it - on another host, and of cause we cannot determine any absolute path remotely.

[ Permlink | « Hide ]

Andras Hatvani - 29/Sep/08 05:36 PM

captureScreenshot is a Java implementation using the AWT; while captureEntirePageScreenshot is based on the Screengrab! Firefox add-on for chrome and uses snapsIE in an experimental mode for IE. This means that this functionality depends on external tools and technologies however, providing a unique way of handling files for similar features is definitely a nice to have thing, thus changing issue type from bug to improvement and reducing priority. In this case it's up to the maintainers of the tools how to handle files.