Yeah I thought about doing that, there's a firefox 'kill' remote command that's supposed to work, on unix anyway. I don't really want to relaunch the browser for each test, it seems like that would slow things down too much, although it would be more hygenic.
I'll try this profile hack, I'm giving it a 50% chance of working. On Fri, Dec 11, 2009 at 8:58 AM, P T Withington <[email protected]> wrote: > As a last resort, I suppose you could somehow have ant quit the browser > each time... I'm not sure how cross-platform this test is. Is it supposed > to be? > > On 2009-12-11, at 08:55, Henry Minsky wrote: > > > On Fri, Dec 11, 2009 at 7:51 AM, P T Withington <[email protected]> wrote: > > > >> If we can't close the window, is there a way to at least reuse the same > >> window? > >> > >> > > The universe seems conspired against being able to even use the same > window > > when > > launching from the command line. > > > > But, I think there's one possible hack I can do, using Raju's tip about > > setting the dom.allow_scripts_to_close_windows flag. I think maybe I can > > make a Firefox .ini profile > > file which contains that flag, and have the "open" command use it when it > > launches firefox. > > Then each app should hopefully be able to close it's own window when it > > completes. > > > > > > > > > > > >> > >> > >> > >> > >> > > On 2009-12-10, at 22:55, Henry Minsky wrote: > >> > >>> I'm trying to clean up the automatic test that spawns one window per > unit > >>> test app. What is the best way to close the > >>> app's containing browser window from inside of the app when it is done > >> with > >>> it's test? > >>> > >>> > >>> > >>> -- > >>> Henry Minsky > >>> Software Architect > >>> [email protected] > >> > >> > > > > > > -- > > Henry Minsky > > Software Architect > > [email protected] > > > -- Henry Minsky Software Architect [email protected]
