Using a workaround to be able to check the contents of a new tab, I get unexpected results. If I play the test case, the following line fails:
storeEval | javascript{"selenium.browserbot.getCurrentWindow().open( , my_window )"} | my_window
附有以下错误信息:
[error] Threw an exception: result is null
The following alternative statements show the exact same symptoms:
getEval | window.open("", "my_window")
getEval | selenium.browserbot.openWindow("", "my_window")
现在,如果我翻一番,那么doesn t就失败了,但它打开了一个新的窗口,我认为最初的解决办法的确是用的(下一个步骤是点击 即<>/em>窗户的链接)。 此时,我可以点击母窗,人工操作下一步骤,以启动链接,人工改用儿童窗口(selectWindow 本人_window)。 它说,它可能发现这一窗口,并手工操作以下步骤,以检查新窗口的内容。
我如何从这里着手适当测试automatic?
Update: There is a built-in action for opening windows, but it also fails. Maybe this verbatim log output can shed some light on what s going on:
[info] Executing: |store | license_window | windowName |
...
[info] Executing: |openWindow | | ${windowName} |
[error] Unexpected Exception: fileName -> chrome://selenium-ide/content/recorder.js, lineNumber -> 74
记录员的有关线:
66: window.open = function(url, windowName, windowFeatures, replaceFlag) {
...
74: if (result.wrappedJSObject) {
75: result = result.wrappedJSObject;
76: }