I'm not sure the root cause which maybe related to Firefox Chrome Security Strategy for -chrome parameter.
Here is a workaround:
Hijack selenium-ide.xpi. Under selenium-ide\content\selenium\ add a file PseudoTestRunner.html
Source:
<html>
<head><title>Pseudo Test Runner - Used for launch Chrome by Cmdline</title></head>
<body>
<script language="javascript">
var strHref;
var intParamsStartIndex;
var strParams;
strHref = window.location.href;
intParamsStartIndex = strHref.indexOf("?");
strParams = strHref.substring(intParamsStartIndex);
window.open("chrome://selenium-ide-testrunner/content/selenium/TestRunner.html" + strParams);
window.close();
</script>
</body>
</html>
Then please always use PseudoTestRunner.html instead of TestRunner.html in cmdline, keep the same parameter list in URL.Refer to topic: http://clearspace.openqa.org/message/51801#51801
Posts
No comments:
Post a Comment