On 10/06/2011 02:17 PM, thron7 wrote: > > Meanwhile, let me put out a few pieces you might find helpful: > > - I think a good point to start is working with the Selenium IDE in > Firefox. The Selenium IDE is a Firefox plugin. You can load your user > extension in there, trigger it through the IDE, and should be able to > debug the code in Firebug. Unfortunately, Firebug won't work with add-on JavaScript (loaded using the chrome:// schema). There's a project called Chromebug (http://getfirebug.com/wiki/index.php/Chromebug) for that, but I never got it to work. It loads, but none of the buttons in the GUI do anything. > > - Of course you can inject "debugger" statements in the user extension, > and run it through a normal test. But that means your user extension > gets loaded from the Selenium RC server into an own browser > window/frame, and you need to debug it there, while your client driver > test script is running. That might prove tedious, and you could run into > all kinds of timing issues. You also would need to package a new > Selenium server jar after every change you make to the extension. I spent quite a bit of time fiddling around with this approach, but couldn't get it to work, either. Here are some things I learned:
It's best to use the Selenium server in interactive mode (by starting it with the -interactive) flag. That way, you can execute commands manually, avoiding any timing issues. Also, repackaging isn't necessary since you can use the -userExtensions option for the server. Of course you still have to restart the server after any change to user-extensions.js. Firebug will only respect "debugger" statements for scripts that were loaded while the Firebug "Script" panel was active, which, by default, it's not. You can get around that by 1) Creating a new Firefox profile, named e.g. Selenium-Debug 2) Starting FF with that profile and installing Firebug 3) Opening about:config and setting the value of extensions.firebug.allPagesActivation to "on" 4) Telling the Selenium server to use that profile: java -jar selenium-server-standalone-2.5.0.jar -interactive -userExtensions /home/dwagner/workspace/qooxdoo.trunk/component/simulator/tool/user-extensions/user-extensions.js -firefoxProfileTemplate /home/dwagner/.mozilla/firefox/vh14mrp0.Selenium-Debug 5) Starting a Firefox session: cmd=getNewBrowserSession&1=*firefox&2=http://localhost Now the Selenium server and the AUT will be loaded in separate Firefox windows, both with Firebug open and activated. But for some reason, Firebug won't recognize the Selenium core scripts, always displaying "there are no scripts on this page" even though they're right there in the HTML <head>. I gave up at this point and went back to tedious manual debugging using Selenium IDE and tons of LOG.debug calls in the user extension. > > - Head over to the Selenium homepage and forum [1], I'm sure there is > good advice concerning your question there. > > T. > > [1] http://seleniumhq.org/ > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
