Using a workaround to check the contents of a new tab, I get unexpected results. If I play in a test case, the following line does not work:
storeEval | javascript{"selenium.browserbot.getCurrentWindow().open('', 'my_window')"} | my_window
with the following error message:
[error] Threw an exception: result is null
The following alternative statements show the same symptoms:
getEval | window.open("", "my_window") getEval | selenium.browserbot.openWindow("", "my_window")
Now, if I double-click on it, it will not work, but it will open a new window, which, it seems to me, is not the original solution (the next step is to click on the link in the parent window, in the end). At this point, I can click on the parent window, manually start the next step to start the link, manually return to the child window ( selectWindow | my_window says that it cannot find this window) and manually complete each of the following steps to check the contents of the new window.
How can I come from here to make the test correctly automatic?
Update. There is a built-in action to open windows, but it also does not work. Perhaps this verbatim conclusion from the magazine may shed light on what is happening:
[info] Executing: |store | license_window | windowName | ... [info] Executing: |openWindow | | ${windowName} | [error] Unexpected Exception: fileName -> chrome://selenium-ide/content/recorder.js, lineNumber -> 74
Relevant lines from recorder.js:
66: window.open = function(url, windowName, windowFeatures, replaceFlag) { ... 74: if (result.wrappedJSObject) { 75: result = result.wrappedJSObject; 76: }