This is an interesting project - it is great to have Chrome support for Watir. It is also an interesting use of the Chrome JavaScript command line debugger. However it is good to hear that you consider moving to a more stable interface. We are currently working on adding a graphical debugger to Chrome to replace the current command line based one. Whether we will keep the command line debugger (in the telnet interface) or not have not been decided. If the command line debugger sticks around relying on the command syntax is rather fragile. Regards, Søren Gjesse
On Wed, Jan 21, 2009 at 6:08 AM, Sai Venkatakrishnan < [email protected]> wrote: > Thanks man... Yeah on the second day we used the js debug shell we > understood that we need a better and stable interface. But at that point js > shell was easier for us to communicate with. > > We have plans to move to Automation Framework soon but need to figure out > how to use it from Ruby and wether I should learn C++ from the begining > again ;). > > Well the difference between Watir and WebDriver. Two different platforms > (Java and Ruby). Different API structures. Different internal workings (Some > drivers of both are common like IE and some like firefox are different). And > different philosphy for development (WebDriver being developer focused > though testers use it and Watir started out as teaching Ruby for testers) > and different communities. Thats what I can think as of now :) > > Regards, > Sai > http://code.google.com/p/chrome-watir > http://code.google.com/p/flash-watir > > > > On Wed, Jan 21, 2009 at 3:06 AM, Patrick Johnson <[email protected]>wrote: > >> This is very cool and interesting. I would recommend seeing if it's >> possible to use the automation framework, as that's likely to be a >> more stable interface. Feel free to send questions to this list >> (that's what it's here for). >> >> Also, I'm curious, what are the differences between Watir and >> WebDriver? They seem to be accomplishing similar goals. >> >> Patrick >> >> >> On Tue, Jan 20, 2009 at 12:52 AM, sai <[email protected]> >> wrote: >> > >> > For the curious yes it does use the js debugger :). I found the >> > automation channel before I found js debugger. But I am really not >> > good in understanding C++ code. I am still reading it and don't know >> > how long I will.... >> > >> > We are actually planning to move to automation framework but we may >> > need your help in this (a lot.) >> > >> > Regards, >> > Sai >> > >> > On Jan 19, 10:58 pm, Evan Martin <[email protected]> wrote: >> >> On Mon, Jan 19, 2009 at 2:06 AM, sai <[email protected]> >> wrote: >> >> > We are happy to announce that the first version of ChromeWatir has >> >> > been released. The API follows a similar convention to Watir (http:// >> >> > wtr.rubygorge.org) for Google Chrome browser. Please visit the >> >> > ChromeWatir Google code >> >> > website for more detailshttp://code.google.com/p/chrome-watir >> >> >> >> For those curious, this appears to use the JS debugger that works over >> >> localhost:12345, not the testing automation framework. >> > > >> > >> > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
