On 04/11/2011 03:21 PM, Jean-Baptiste BRIAUD -- Novlog wrote: > > On 11 avr. 2011, at 14:30, Daniel Wagner wrote: > >> Hi JBB, >> >> On 04/11/2011 10:27 AM, Jean-Baptiste BRIAUD -- Novlog wrote: >>> 3. Selenium tests >>> I currently fight with our Selenium test that are failing with only a >>> timeout as a hint ... >>> We are still using an old Selenium version, what is the recommended >>> Selenium version for qooxdoo 1.4 ? >>> Our tests are using FF 3.6.16 since FF4 doesn't launch using Selenium >>> (including with the hack I've found to replace some 3.6.* by 4.* in some >>> Selenium file). >>> Apparently, with qooxdoo 1.4, I got a "script take too long" dialog box >>> during our tests, so the time out ... still under investigation ... >> >> 1.0.3 is the Selenium version I've had the most success with in terms of >> browser compatibility. >> > I think that's the one we're using. > >> This is how I got FF4 to run with our tests: >> 1) Create a new Firefox profile (by starting Firefox with the -P >> option), naming it e.g. "FF4-Selenium". >> 2) In that profile, disable popup blocking and add a manual proxy >> configuration, using your Selenium server's host name and port number. >> 3) Configure your test to use the custom launcher and the new profile: >> *custom /path/to/firefox/firefox -P FF4-Selenium >> > > Well, I'm not sure ... > I'm using Selenium for testing as much as possible in real situation. > So, if the "slow script" dialog appears in real situation, I'm OK to fail my > tests. > So basically, I'm not sure it is a good idea to disable that dialog on test > server. > What do you think ? > > also, I didn't use that Firefox profile mainly because it works without and I > launching the test on a test server that is not use for browsing. > Would you advise us to use such profile ? if yes why ? > Is it for FF4 ? Currently, we're still using 3.1.16 for our tests.
Yes, the profile workaround is just to get FF4 to launch at all. Without that, I just get a 404 error since Selenium can't configure the browser to use the server as a proxy. This won't fix any long running script warnings. > >> As for the long running script warning, I'd suggest taking a close look >> at Selenium's log window while the test is running. That should give you >> a better idea if what's going wrong. >> > This happen during a table cell edition but I really don't understand why, > obviously link with something new in qooxdoo 1.4 ... > Unfortunately, I have nothing more to give here that could help you helping > me :-) There's a known bug where a resize event will cause the table to enter an infinite loop, ultimately triggering the long running script dialog: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4934 (Description says TreeVirtual but the table uses the same code) Could this be the issue you're seeing? Regards, Daniel ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
