[prev in list] [next in list] [prev in thread] [next in thread] 

List:       selenium-commits
Subject:    [Selenium-commits] [JIRA] Commented: (SEL-167)
From:       "Nelson Sproul (JIRA)" <jira () public ! thoughtworks ! org>
Date:       2005-12-23 0:44:00
Message-ID: 107325580.1135298640300.JavaMail.oqa-j2ee () openqa01 ! managed ! contegix ! com
[Download RAW message or body]

    [ http://jira.openqa.org/browse/SEL-167?page=comments#action_12582 ] 

Nelson Sproul commented on SEL-167:
-----------------------------------

This bug applies to all browsers; it is a bit less noticeable w/ firefox because the \
tabbed browsing means that only new tabs are opened, as opposed to full-fledged \
windows.

This failure of the browser to exit is more than just an esthetic inconvenience \
because the selenium pages apparently hold some crucial resource which does not allow \
an infinite number of browser sessions to peacefully coexist.  In fact, with Internet \
Explorer and FireFox, the limit is only two!  When the attempt is made to launch the \
third browser session, the page does not load, and the browser just shows a blank \
screen.

To work around this problem, I added code to jump away from the selenium test page \
when the testComplete verb executes.  This solves the problem I describe above, but \
the drawback is that you don't see the selenium page anymore once the test code has \
finished executing.  The log window is fortunately undisturbed, so at least that \
information is still around.

Here's the glorious diff:

diff -r -b $OLD/shared/p4/Tools/selenium/javascript/SeleneseRunner.html \
/home/nelsons/shared/p4/Tools/selenium/javascript/SeleneseRunner.html 152a154
> 	window.location = "about:blank";

Btw, I think the priority of this issue should be raised, because it effectively \
prevents anything but the smallest scale automated testing from driven mode.



> SystemDefaultBrowserLauncher() does not kill IE after test is done
> ------------------------------------------------------------------
> 
> Key: SEL-167
> URL: http://jira.openqa.org/browse/SEL-167
> Project: Selenium
> Type: Bug
> Components: Standalone Server
> Versions: 0.6
> Environment: Windows 2k3, IE 6
> Reporter: Nelson Sproul
> Priority: Minor

> 
> 
> If you use SystemDefaultBrowserLauncher() to spawn your browsers, then the browser \
> windows remain after the test.  So if you run the test 3 times, you end up w/ 3 IE \
> windows left on your desktop. SystemDefaultBrowserLauncher() is the method used in \
> the code that ships. A workaround is to switch to using WindowsIEBrowserLauncher(), \
> which kills IE after the test.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

_______________________________________________
Selenium-commits mailing list
Selenium-commits@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-commits


[prev in list] [next in list] [prev in thread] [next in thread]