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

List:       selenium-commits
Subject:    [Selenium-commits] [JIRA] Commented: (SEL-174) Driven mode logging
From:       "Mike Williams (JIRA)" <jira () public ! thoughtworks ! org>
Date:       2005-12-17 8:59:02
Message-ID: 91457837.1134809942134.JavaMail.oqa-j2ee () openqa01 ! managed ! contegix ! com
[Download RAW message or body]

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

Mike Williams commented on SEL-174:
-----------------------------------

Perhaps the best bet is to pull the logging iframe into the main SeleneseRunner \
window, and push the AUT frame into it's own, top-level window? Or, would that create \
the same issues re browser shutdown?

I don't think it reasonable to restrict Selenium (itself, plus AUT, plus logging) to \
a single top-level window ... at least, not once we support testing of multi-frame, \
multi-window apps.  Perhaps instead Selenium could be instructed to close any \
"outlying" windows once testing has "finished"?

> Driven mode logging doesn't work
> --------------------------------
> 
> Key: SEL-174
> URL: http://jira.openqa.org/browse/SEL-174
> Project: Selenium
> Type: Bug
> Components: SeleneseRunner, Drivers - Ruby, Drivers - Plone, Drivers - .Net, \
>                 Drivers - Java
> Versions: 0.6
> Environment: IE6 with Java Driver 0.6.0 on Windows 2003
> Reporter: Dan Fabulich

> 
> 
> Normally Selenium logging is done by having the user manually open the logging \
> window in the browser prior to launching the tests.  But in driven mode, the \
> browser automatically starts running tests immediately upon startup; there's no \
> time to click on the "Show Log" button to get the logs. If you add a direct call to \
> LOG.show() in the onload handler for SeleneseRunner.html, the log will open, but \
> then the WindowsIEBrowserLauncher will be unable to close all browser windows at \
> shutdown time.  This will cause the RealDealIntegrationTest to fail.  (It looks \
> like possibly another caching problem...?) The SeleneseRunner needs to not use a \
> separate window; it should use an iframe instead.  Furthermore, it needs to be \
> possible to use query arguments to set the logging level from the driver side, so \
> that logging can occur automatically.

-- 
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]