From bret at pettichord.com Tue Jan 16 18:17:17 2007 From: bret at pettichord.com (Bret Pettichord) Date: Tue, 16 Jan 2007 17:17:17 -0600 Subject: [Wtr-core] Reuniting Watir Message-ID: One of the things that happened at this week's AWTA conference was that Bob and i wrote a quick spike of MineralWatir, a Watir-like ruby interface to Selenium-RC. Here is the code: http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir After we wrote this, we discussed how to move forward. I suggested a separate project, much like FireWatir or SafariWatir, but Bob strongly felt that we should be developing these code bases in a single repository and maximize the amount of shared code. We walked throught the Watir and FireWatir code bases to get a sense of how the code could be refactored to support this. The tentative plan that we discussed would be to refactor the Watir code post 1.5. Angrez actually started this refactoring some time ago with FireWatir, unfortunately his separation did not get committed back to the Watir trunk. Watir 2.0 would be label for the single gem that would support multiple browsers. My view is that joining the projects would necessitate putting them under continuous integration. I'm already seeing problems with Watir-IE because we don't have it. Having multiple "targets" would only exacerbate the problem. We may also need to have a way to tag tests, to indicate which targets they should be run against (and be expected to pass). Doing this will require a lot of coordination and discussion. Obviously, we would all like to implement the common Watir API, but there are also features that either only make sense for one target (like IE's showModalDialog) or which simply are easier to support in one implementation than another (e.g. frame support). Eventually we would need to figure out how to ensure that tests authored with one "thing" (i'm not sure what to call these different watir's) can run on another. But first, would you be be willing and interested in helping recombine these projects? If there is agreement on this point, i think we should probably move a discussion of details to wtr-development. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070116/7d22ebf5/attachment-0001.html From paul.rogers at shaw.ca Tue Jan 16 23:09:50 2007 From: paul.rogers at shaw.ca (Paul Rogers) Date: Tue, 16 Jan 2007 21:09:50 -0700 Subject: [Wtr-core] Reuniting Watir References: Message-ID: <018501c739ed$55c932f0$6400a8c0@laptop> I havent done much with rumba, but if I do then yes. Id be interested in doing some continuos integration stuff, more for my own interest. I'll see if I can do something with one of my old PCs Paul ----- Original Message ----- From: Bret Pettichord To: Bob Cotton ; Bob Cotton ; Angrez Singh ; Dave Hoover ; Paul Rogers ; Charley Baker Cc: wtr-core at rubyforge.org Sent: Tuesday, January 16, 2007 4:17 PM Subject: Reuniting Watir One of the things that happened at this week's AWTA conference was that Bob and i wrote a quick spike of MineralWatir, a Watir-like ruby interface to Selenium-RC. Here is the code: http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir After we wrote this, we discussed how to move forward. I suggested a separate project, much like FireWatir or SafariWatir, but Bob strongly felt that we should be developing these code bases in a single repository and maximize the amount of shared code. We walked throught the Watir and FireWatir code bases to get a sense of how the code could be refactored to support this. The tentative plan that we discussed would be to refactor the Watir code post 1.5. Angrez actually started this refactoring some time ago with FireWatir, unfortunately his separation did not get committed back to the Watir trunk. Watir 2.0 would be label for the single gem that would support multiple browsers. My view is that joining the projects would necessitate putting them under continuous integration. I'm already seeing problems with Watir-IE because we don't have it. Having multiple "targets" would only exacerbate the problem. We may also need to have a way to tag tests, to indicate which targets they should be run against (and be expected to pass). Doing this will require a lot of coordination and discussion. Obviously, we would all like to implement the common Watir API, but there are also features that either only make sense for one target (like IE's showModalDialog) or which simply are easier to support in one implementation than another ( e.g. frame support). Eventually we would need to figure out how to ensure that tests authored with one "thing" (i'm not sure what to call these different watir's) can run on another. But first, would you be be willing and interested in helping recombine these projects? If there is agreement on this point, i think we should probably move a discussion of details to wtr-development. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070116/b0d01c82/attachment.html From dave.hoover at gmail.com Wed Jan 17 07:24:03 2007 From: dave.hoover at gmail.com (Dave Hoover) Date: Wed, 17 Jan 2007 06:24:03 -0600 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: Message-ID: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> If you're able to refactor Watir to abstract away all of the Windows-specific functionality, I would definitely like to take advantage of that. An issue I see with "a single gem that supports multiple browsers" is that the safariwatir.gem depends on rb-appscript.gem, which can only be installed on Macs. On 1/16/07, Bret Pettichord wrote: > One of the things that happened at this week's AWTA conference was that Bob > and i wrote a quick spike of MineralWatir, a Watir-like ruby interface to > Selenium-RC. Here is the code: > http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir > > After we wrote this, we discussed how to move forward. I suggested a > separate project, much like FireWatir or SafariWatir, but Bob strongly felt > that we should be developing these code bases in a single repository and > maximize the amount of shared code. We walked throught the Watir and > FireWatir code bases to get a sense of how the code could be refactored to > support this. > > The tentative plan that we discussed would be to refactor the Watir code > post 1.5. Angrez actually started this refactoring some time ago with > FireWatir, unfortunately his separation did not get committed back to the > Watir trunk. Watir 2.0 would be label for the single gem that would support > multiple browsers. > > My view is that joining the projects would necessitate putting them under > continuous integration. I'm already seeing problems with Watir-IE because we > don't have it. Having multiple "targets" would only exacerbate the problem. > We may also need to have a way to tag tests, to indicate which targets they > should be run against (and be expected to pass). > > Doing this will require a lot of coordination and discussion. > > Obviously, we would all like to implement the common Watir API, but there > are also features that either only make sense for one target (like IE's > showModalDialog) or which simply are easier to support in one implementation > than another ( e.g. frame support). Eventually we would need to figure out > how to ensure that tests authored with one "thing" (i'm not sure what to > call these different watir's) can run on another. > > But first, would you be be willing and interested in helping recombine these > projects? If there is agreement on this point, i think we should probably > move a discussion of details to wtr-development. > > Bret > > > From charley.baker at gmail.com Wed Jan 17 15:21:07 2007 From: charley.baker at gmail.com (Charley Baker) Date: Wed, 17 Jan 2007 13:21:07 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: Message-ID: In looking at the future direction for Watir, it seems pretty clear that one of the needs is the ability to run against multiple browsers, which until now has been solved by multiple projects. Unifying the different projects so that we have a single entry point will make it easier for users to understand and hopefully help when the time comes to evaluate the various testing options. In other words I'm very much in favor of this idea. I'd agree with a single repository, the single gem could also deal with platform issues as Dave mentioned installing only what's applicable. I'm more than willing to help as long as the project heads are amenable to supporting this concept. Do we also plan support for Selenium-RC? I'll vote for moving this topic to the watir dev list. -Charley On 1/16/07, Bret Pettichord wrote: > > One of the things that happened at this week's AWTA conference was that > Bob and i wrote a quick spike of MineralWatir, a Watir-like ruby interface > to Selenium-RC. Here is the code: > http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir > > After we wrote this, we discussed how to move forward. I suggested a > separate project, much like FireWatir or SafariWatir, but Bob strongly felt > that we should be developing these code bases in a single repository and > maximize the amount of shared code. We walked throught the Watir and > FireWatir code bases to get a sense of how the code could be refactored to > support this. > > The tentative plan that we discussed would be to refactor the Watir code > post 1.5. Angrez actually started this refactoring some time ago with > FireWatir, unfortunately his separation did not get committed back to the > Watir trunk. Watir 2.0 would be label for the single gem that would > support multiple browsers. > > My view is that joining the projects would necessitate putting them under > continuous integration. I'm already seeing problems with Watir-IE because we > don't have it. Having multiple "targets" would only exacerbate the problem. > We may also need to have a way to tag tests, to indicate which targets they > should be run against (and be expected to pass). > > Doing this will require a lot of coordination and discussion. > > Obviously, we would all like to implement the common Watir API, but there > are also features that either only make sense for one target (like IE's > showModalDialog) or which simply are easier to support in one implementation > than another ( e.g. frame support). Eventually we would need to figure out > how to ensure that tests authored with one "thing" (i'm not sure what to > call these different watir's) can run on another. > > But first, would you be be willing and interested in helping recombine > these projects? If there is agreement on this point, i think we should > probably move a discussion of details to wtr-development. > > Bret > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/6275fe39/attachment.html From bob.cotton at rallydev.com Wed Jan 17 15:33:46 2007 From: bob.cotton at rallydev.com (Bob Cotton) Date: Wed, 17 Jan 2007 13:33:46 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: (Charley Baker's message of "Wed, 17 Jan 2007 13:21:07 -0700") References: Message-ID: Selenium-RC (aka MineralWatir) is where I come in :-) - Bob "Charley Baker" writes: > In looking at the future direction for Watir, it seems pretty clear that > one of the needs is the ability to run against multiple browsers, which > until now has been solved by multiple projects. Unifying the different > projects so that we have a single entry point will make it easier for > users to understand and hopefully help when the time comes to evaluate the > various testing options. > > In other words I'm very much in favor of this idea. I'd agree with a > single repository, the single gem could also deal with platform issues as > Dave mentioned installing only what's applicable. I'm more than willing to > help as long as the project heads are amenable to supporting this concept. > Do we also plan support for Selenium-RC? > > I'll vote for moving this topic to the watir dev list. > > -Charley > > On 1/16/07, Bret Pettichord < [1]bret at pettichord.com> wrote: > > One of the things that happened at this week's AWTA conference was that > Bob and i wrote a quick spike of MineralWatir, a Watir-like ruby > interface to Selenium-RC. Here is the code: > [2]http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir > > After we wrote this, we discussed how to move forward. I suggested a > separate project, much like FireWatir or SafariWatir, but Bob strongly > felt that we should be developing these code bases in a single > repository and maximize the amount of shared code. We walked throught > the Watir and FireWatir code bases to get a sense of how the code could > be refactored to support this. > > The tentative plan that we discussed would be to refactor the Watir code > post 1.5. Angrez actually started this refactoring some time ago with > FireWatir, unfortunately his separation did not get committed back to > the Watir trunk. Watir 2.0 would be label for the single gem that would > support multiple browsers. > > My view is that joining the projects would necessitate putting them > under continuous integration. I'm already seeing problems with Watir-IE > because we don't have it. Having multiple "targets" would only > exacerbate the problem. We may also need to have a way to tag tests, to > indicate which targets they should be run against (and be expected to > pass). > > Doing this will require a lot of coordination and discussion. > > Obviously, we would all like to implement the common Watir API, but > there are also features that either only make sense for one target (like > IE's showModalDialog) or which simply are easier to support in one > implementation than another ( e.g. frame support). Eventually we would > need to figure out how to ensure that tests authored with one "thing" > (i'm not sure what to call these different watir's) can run on another. > > But first, would you be be willing and interested in helping recombine > these projects? If there is agreement on this point, i think we should > probably move a discussion of details to wtr-development. > Bret > > References > > Visible links > 1. mailto:bret at pettichord.com > 2. http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir -- Bob Cotton Test Architect -- Rally Software -- rallydev.com http://www.testarchitecture.com/blog From paul.rogers at shaw.ca Wed Jan 17 15:42:36 2007 From: paul.rogers at shaw.ca (Paul Rogers) Date: Wed, 17 Jan 2007 13:42:36 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: Message-ID: as well as multi browsers, this also opens up the multi platform issue. I have a super powerful linux box at work thats only purpose at the moment is to keep me warm, so I will be trying firewatir on it soon. I'll also be installing it on my home linux server. Im not hugely knowlegeable about linux, and Ive been wanting an opportunity to spend more time on it, and this seems as good as any. I have no knowledge of macs, so we would need to find someone willing to try this stuff on macs, and also answer questions on the list if possible Paul ----- Original Message ----- From: Charley Baker Date: Wednesday, January 17, 2007 1:21 pm Subject: Re: Reuniting Watir > In looking at the future direction for Watir, it seems pretty > clear that > one of the needs is the ability to run against multiple browsers, > whichuntil now has been solved by multiple projects. Unifying the > differentprojects so that we have a single entry point will make > it easier for users > to understand and hopefully help when the time comes to evaluate > the various > testing options. > > In other words I'm very much in favor of this idea. I'd agree > with a single > repository, the single gem could also deal with platform issues as > Davementioned installing only what's applicable. I'm more than > willing to help > as long as the project heads are amenable to supporting this > concept. Do we > also plan support for Selenium-RC? > > I'll vote for moving this topic to the watir dev list. > > -Charley > > On 1/16/07, Bret Pettichord wrote: > > > > One of the things that happened at this week's AWTA conference > was that > > Bob and i wrote a quick spike of MineralWatir, a Watir-like ruby > interface> to Selenium-RC. Here is the code: > > http://awta.wikispaces.com/Common+Driver+for+Selenium+and+Watir > > > > After we wrote this, we discussed how to move forward. I > suggested a > > separate project, much like FireWatir or SafariWatir, but Bob > strongly felt > > that we should be developing these code bases in a single > repository and > > maximize the amount of shared code. We walked throught the Watir and > > FireWatir code bases to get a sense of how the code could be > refactored to > > support this. > > > > The tentative plan that we discussed would be to refactor the > Watir code > > post 1.5. Angrez actually started this refactoring some time ago > with> FireWatir, unfortunately his separation did not get > committed back to the > > Watir trunk. Watir 2.0 would be label for the single gem that would > > support multiple browsers. > > > > My view is that joining the projects would necessitate putting > them under > > continuous integration. I'm already seeing problems with Watir- > IE because we > > don't have it. Having multiple "targets" would only exacerbate > the problem. > > We may also need to have a way to tag tests, to indicate which > targets they > > should be run against (and be expected to pass). > > > > Doing this will require a lot of coordination and discussion. > > > > Obviously, we would all like to implement the common Watir API, > but there > > are also features that either only make sense for one target > (like IE's > > showModalDialog) or which simply are easier to support in one > implementation> than another ( e.g. frame support). Eventually we > would need to figure out > > how to ensure that tests authored with one "thing" (i'm not sure > what to > > call these different watir's) can run on another. > > > > But first, would you be be willing and interested in helping > recombine> these projects? If there is agreement on this point, i > think we should > > probably move a discussion of details to wtr-development. > > > > Bret > > > > > > > From christopher.mcmahon at gmail.com Wed Jan 17 16:01:56 2007 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Wed, 17 Jan 2007 13:01:56 -0800 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: Message-ID: <72799cd70701171301n4373b1ag36e8d688dbd9e6b9@mail.gmail.com> > > > I have no knowledge of macs, so we would need to find someone willing to > try this stuff on macs, and also answer questions on the list if possible I have a couple of macs at home running different versions of OSX (with maybe another on the way) and I've been following Dave's progress on SafariWatir but without much motivation to actually try it out. I would be willing to be a Customer on the Mac side and chime in here and there on the dev side where I could say something useful. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/2cc65e23/attachment.html From bret at pettichord.com Wed Jan 17 16:03:52 2007 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 17 Jan 2007 15:03:52 -0600 Subject: [Wtr-core] Reuniting Watir In-Reply-To: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> Message-ID: On 1/17/07, Dave Hoover wrote: > > An issue I see with "a single gem that supports multiple browsers" is > that the safariwatir.gem depends on rb-appscript.gem, which can only > be installed on Macs. I see your point. Watir::IE currently installs a modified win32ole.so and an Autoit DLL and it would probably be rude to install these on a Mac. So maybe we'd have to create separate Gems for Windows, Mac and Linux. I guess the real question is whether there is interest in migrating the code from the different projects into a single repository. I guess we would start with most of the code in platform/browser specific files and then refactor the repeated code into common code. Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/41784228/attachment.html From dave.hoover at gmail.com Wed Jan 17 16:13:53 2007 From: dave.hoover at gmail.com (Dave Hoover) Date: Wed, 17 Jan 2007 15:13:53 -0600 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> Message-ID: <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> > I guess the real question is whether there is interest in migrating the code > from the different projects into a single repository. I am open to migrating to a single repository if I could take advantage of a reusable "core" Watir. > I guess we would start > with most of the code in platform/browser specific files and then refactor > the repeated code into common code. If the Windows-specific pieces of Watir::IE could be extracted to an IE-specific driver, that would be a great start. As I have developed Watir::Safari, I've tried to keep the core Watir classes separate from the classes responsible for communicating directly with Safari (via JavaScript via Apple Events), so it would remove/improve a lot of my code if I had a "core" Watir to build on. From charley.baker at gmail.com Wed Jan 17 16:29:39 2007 From: charley.baker at gmail.com (Charley Baker) Date: Wed, 17 Jan 2007 14:29:39 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> Message-ID: It seems as though there is a lot of interest in unifying the projects. II'd suggest moving this over to the dev list. Here's my breakdown of leads: Bret: Watir Dave: SafariWatir Angrez: FireWatir Bob: Selenium RC integration - MineralWatir Can we set up a regular weekly meeting on Skype, phone conference, irc, or whatever, for this project? -Charley On 1/17/07, Dave Hoover wrote: > > > I guess the real question is whether there is interest in migrating the > code > > from the different projects into a single repository. > > I am open to migrating to a single repository if I could take > advantage of a reusable "core" Watir. > > > I guess we would start > > with most of the code in platform/browser specific files and then > refactor > > the repeated code into common code. > > If the Windows-specific pieces of Watir::IE could be extracted to an > IE-specific driver, that would be a great start. As I have developed > Watir::Safari, I've tried to keep the core Watir classes separate from > the classes responsible for communicating directly with Safari (via > JavaScript via Apple Events), so it would remove/improve a lot of my > code if I had a "core" Watir to build on. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/821edd89/attachment.html From bret at pettichord.com Wed Jan 17 16:45:22 2007 From: bret at pettichord.com (Bret Pettichord) Date: Wed, 17 Jan 2007 15:45:22 -0600 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> Message-ID: > > Bret: Watir I suggest that we start calling this implementation Watir::IE or something similar, since the purpose of this discussion is to brand "Watir" as cross-platform cross-browser solution (or set of solutions). Other suggestions? Bret -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/e4f412bc/attachment.html From bob.cotton at rallydev.com Wed Jan 17 16:46:57 2007 From: bob.cotton at rallydev.com (Bob Cotton) Date: Wed, 17 Jan 2007 14:46:57 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: (Charley Baker's message of "Wed, 17 Jan 2007 14:29:39 -0700") References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> Message-ID: Attempting to move to wtr-development. everyone subscribed? "Charley Baker" writes: > It seems as though there is a lot of interest in unifying the projects. > II'd suggest moving this over to the dev list. Here's my breakdown of > leads: > Bret: Watir > Dave: SafariWatir > Angrez: FireWatir > Bob: Selenium RC integration - MineralWatir > > Can we set up a regular weekly meeting on Skype, phone conference, irc, or > whatever, for this project? Weekly meetings sound like a good idea. Bret had mentioned that this would be a post 1.5 plan. Is there a plan for the 1.5 release? -- Bob Cotton Test Architect -- Rally Software -- rallydev.com http://www.testarchitecture.com/blog From bob.cotton at rallydev.com Wed Jan 17 16:55:53 2007 From: bob.cotton at rallydev.com (Bob Cotton) Date: Wed, 17 Jan 2007 14:55:53 -0700 Subject: [Wtr-core] Reuniting Watir In-Reply-To: (Bret Pettichord's message of "Wed, 17 Jan 2007 15:45:22 -0600") References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> Message-ID: "Bret Pettichord" writes: > Bret: Watir > > I suggest that we start calling this implementation Watir::IE or something > similar, since the purpose of this discussion is to brand "Watir" as > cross-platform cross-browser solution (or set of solutions). Other > suggestions? Watirie Magellan http://en.wikipedia.org/wiki/List_of_maritime_explorers -Bob -- Bob Cotton Test Architect -- Rally Software -- rallydev.com http://www.testarchitecture.com/blog From christopher.mcmahon at gmail.com Wed Jan 17 17:04:51 2007 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Wed, 17 Jan 2007 14:04:51 -0800 Subject: [Wtr-core] Reuniting Watir In-Reply-To: References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> Message-ID: <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com> WinWatir On 1/17/07, Bob Cotton wrote: > > "Bret Pettichord" writes: > > > Bret: Watir > > > > I suggest that we start calling this implementation Watir::IE or > something > > similar, since the purpose of this discussion is to brand "Watir" as > > cross-platform cross-browser solution (or set of solutions). Other > > suggestions? > > Watirie > Magellan > http://en.wikipedia.org/wiki/List_of_maritime_explorers > > -Bob > > -- > Bob Cotton > Test Architect -- Rally Software -- rallydev.com > http://www.testarchitecture.com/blog > _______________________________________________ > Wtr-core mailing list > Wtr-core at rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-core > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/16901d50/attachment.html From paul.rogers at shaw.ca Wed Jan 17 23:22:21 2007 From: paul.rogers at shaw.ca (Paul Rogers) Date: Wed, 17 Jan 2007 21:22:21 -0700 Subject: [Wtr-core] Reuniting Watir References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com> Message-ID: <004201c73ab8$3f96cf30$6400a8c0@laptop> Watir 'ole as in Watir Hole ? Say it quick and it works ----- Original Message ----- From: Chris McMahon To: wtr-core at rubyforge.org Cc: wtr-development at rubyforge.org ; Bob Cotton Sent: Wednesday, January 17, 2007 3:04 PM Subject: Re: [Wtr-core] Reuniting Watir WinWatir On 1/17/07, Bob Cotton wrote: "Bret Pettichord" writes: > Bret: Watir > > I suggest that we start calling this implementation Watir::IE or something > similar, since the purpose of this discussion is to brand "Watir" as > cross-platform cross-browser solution (or set of solutions). Other > suggestions? Watirie Magellan http://en.wikipedia.org/wiki/List_of_maritime_explorers -Bob -- Bob Cotton Test Architect -- Rally Software -- rallydev.com http://www.testarchitecture.com/blog _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core ------------------------------------------------------------------------------ _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/f020aa65/attachment-0001.html From scott at hanselman.com Thu Jan 18 02:14:05 2007 From: scott at hanselman.com (Scott Hanselman) Date: Wed, 17 Jan 2007 23:14:05 -0800 Subject: [Wtr-core] Reuniting Watir In-Reply-To: <004201c73ab8$3f96cf30$6400a8c0@laptop> References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com> <004201c73ab8$3f96cf30$6400a8c0@laptop> Message-ID: <000101c73ad0$3dfdcbc0$b9f96340$@com> I vote for SparklingWatir or MineralWatir. No reason for it to make sense. Scott Hanselman From: wtr-core-bounces at rubyforge.org [mailto:wtr-core-bounces at rubyforge.org] On Behalf Of Paul Rogers Sent: Wednesday, January 17, 2007 8:22 PM To: wtr-core at rubyforge.org Subject: Re: [Wtr-core] Reuniting Watir Watir 'ole as in Watir Hole ? Say it quick and it works ----- Original Message ----- From: Chris McMahon To: wtr-core at rubyforge.org Cc: wtr-development at rubyforge.org ; Bob Cotton Sent: Wednesday, January 17, 2007 3:04 PM Subject: Re: [Wtr-core] Reuniting Watir WinWatir On 1/17/07, Bob Cotton wrote: "Bret Pettichord" writes: > Bret: Watir > > I suggest that we start calling this implementation Watir::IE or something > similar, since the purpose of this discussion is to brand "Watir" as > cross-platform cross-browser solution (or set of solutions). Other > suggestions? Watirie Magellan http://en.wikipedia.org/wiki/List_of_maritime_explorers -Bob -- Bob Cotton Test Architect -- Rally Software -- rallydev.com http://www.testarchitecture.com/blog _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core _____ _______________________________________________ Wtr-core mailing list Wtr-core at rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-core -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070117/7b42a2cf/attachment.html From christopher.mcmahon at gmail.com Thu Jan 18 02:40:52 2007 From: christopher.mcmahon at gmail.com (Chris McMahon) Date: Wed, 17 Jan 2007 23:40:52 -0800 Subject: [Wtr-core] Reuniting Watir In-Reply-To: <000101c73ad0$3dfdcbc0$b9f96340$@com> References: <11c8704e0701170424o5d376c7ei3688bdc8737a6c33@mail.gmail.com> <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com> <004201c73ab8$3f96cf30$6400a8c0@laptop> <000101c73ad0$3dfdcbc0$b9f96340$@com> Message-ID: <72799cd70701172340j7babdae0k5904fa053f509942@mail.gmail.com> > I vote for SparklingWatir or MineralWatir. No reason for it to make sense. SpringWatir, because it was the source. From sy1234 at gmail.com Thu Jan 18 04:09:47 2007 From: sy1234 at gmail.com (Sy Ali) Date: Thu, 18 Jan 2007 04:09:47 -0500 Subject: [Wtr-core] Reuniting Watir In-Reply-To: <72799cd70701172340j7babdae0k5904fa053f509942@mail.gmail.com> References: <11c8704e0701171313v792aa357y8bb8177afa9a6094@mail.gmail.com> <72799cd70701171404w7305b1fcoe02e044d0f2dea7e@mail.gmail.com> <004201c73ab8$3f96cf30$6400a8c0@laptop> <000101c73ad0$3dfdcbc0$b9f96340$@com> <72799cd70701172340j7babdae0k5904fa053f509942@mail.gmail.com> Message-ID: <1e55af990701180109j25181efbj93baf51d897ca22b@mail.gmail.com> On 1/18/07, Chris McMahon wrote: > > I vote for SparklingWatir or MineralWatir. No reason for it to make sense. > > SpringWatir, because it was the source. SwampWater, because it's old. ;) From angrez at gmail.com Sat Jan 20 04:29:06 2007 From: angrez at gmail.com (Angrez Singh) Date: Sat, 20 Jan 2007 14:59:06 +0530 Subject: [Wtr-core] Fwd: Watir Unification In-Reply-To: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com> References: <7661e6730701200104u57839df5k78bf46b4a7bb27a1@mail.gmail.com> Message-ID: Hi, Here's what Amit (owner of FireWatir & man behind the idea of FireWatir) has to say about the unification of Watir. I would like the owner of 'wtr-development' and 'wtr-core' group to add him to the mailing list. His e-mail id is: amit.garde at gmail.com. 0. I think unification is a good idea and I would vote for it, based > on two primary reasons: > -- A. I think unification (where Watir functionality is largely > brwoser independent) is better from the point of view of end users who > need to test on multiple browsers and platforms, because they need > only learn Watir, and then be able to script test cases that will run > unchanged on all the browsers and platforms of interest. This reduces > the cost, effort, and time in building and maintaining a test suite > for multiple browers and platforms and hence should make Watir a more > attractive option for people who require multi-browser and platform > support. > > --B More philosophically, the web application testing intention is > conceptually separate from the specifics of the browser being used to > test the web app, so the unification will probably support this > philosophical perspective as well. > > 1. I think having a common web-application test specific API, as a > layer that is conceptually separate from and implemented on top of > individual browser specific layers is also a good idea. If this is > going to be one of the results of unification, I think it is a good > thing in itself. > > 2. Given issues with specific platforms and more particularly with > differences in browser features and how easy or otherwise it is to > implement specific web app test functionality in a given browser (for > exanmple xpath based element searching is much easier to do with > Firefox than with IE) the API, features, and structure of the Web app > test layer (which will need to be supplied with concrete > implementations by the browser specific layers) will need to be > carefully discussed and designed. > > Amit - Angrez -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/wtr-core/attachments/20070120/45dd802b/attachment.html