On Aug 7, 10:13 pm, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > rama wrote: > > That was a nice suggestion but it would require modification to the > > site to be tested. > > Not at all. You can put the site in a display:none chrome <xul:browser> > trivially, no modifications required (other than to the Firefox source, > or you can use an extension to accomplish the same thing). > > > Moreover the tests check for visibility of certain > > elements. > > Visibility testing implies having to do layout. How were you going to > do it otherwise, exactly? > > Sounds to me like you're pretty confused about what you want, to be > honest. Can you clearly explain exactly what you're doing and what the > problem you're trying to solve is? > > -Boris
Thanks for the chrome xul pointer. I will read about them and get back to you if I am unable to implement it. Visibility details can be obtained from dom tree. Selenium provides methods to say whether the element is visible or invisible(display:none). Our website would be a heavy weight web site with lots of components. Testing here involves checking if all the components work correctly from the UI, the correct javascript events are triggered and check the DOM status for each of these actions. The pages take considerable time to load on the browser. Hence I wanted to disable layout. In other words I wanted a browser which does everything except for rendering on screen. I can achieve what I want the same thing with HttpUnit which is a headless browser. However HttpUnit uses rhino as javascript engine and is not able to handle the current codebase. Hence I wanted to know if I can operate firefox in headless mode, so that time taken for regression testing is reduced. Thanks, rama _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
