Re: [wtr-general] Upgrading anxiety
On Saturday, December 31, 2011, Jarmo Pertman jarm...@gmail.com wrote: This list is not up to date anymore - should we just delete the statements which aren't true anymore so it would reflect the actual state? I think anybody can edit wiki pages at github, and I think you have the most knowledge about what needs to be fixed there. Željko -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Upgrading anxiety
On Thu, Dec 29, 2011 at 11:34 PM, Lisa Crispin lisa.cris...@gmail.com wrote: I can't live without these scripts, so I don't want to break them. There is a setting in watir 2.x to keep the old 1-based indexing (instead of using the new 0-based). If you are using indexes, that could break a lot of your code. From http://watir.com/2011/08/11/watir-2-0: Watir.options[:zero_based_indexing] = false Is there a central location with this information that I just haven't found yet? I think this is all we have: https://github.com/jarib/watir-webdriver/wiki/Comparison-with-Watir-1.X If I install the latest Ruby and Watir/WebDriver, and our scripts don't work, can I back up to the old versions again? I think the newest watir gem should work on your ruby. So, the easiest thing would be to just upgrade watir gem and try. If you do not like it, just gem uninstall watir at the command line, and it will ask you which version you want to uninstall. You can also install watir-webdriver gem, try it and see if you like it. I think it should also work on your version of ruby. I try to keep installation instructions up to date: https://github.com/zeljkofilipin/watirbook/tree/master/installation I would hate to abandon Watir and the excellent scripts we have, but I don't get any support from my team on this. They are keen to try Selenium. This is not the first time I have heard this. Some people would like to use Watir, some Selenium. The questions is why would they switch to Selenium? Would it look good on their CV? Or they prefer Java (or another language)? Something else? If they would like to try selenium, but stick with ruby, they can try selenium-webdriver gem. As far as I understood it, watir-webdriver gem just adds watir API on top of selenium-webdriver gem. Alister has been writing about different browser automation tools, for example: http://watirmelon.com/2011/12/03/a-tale-of-three-ruby-automated-testing-apis-redux/ If you have any problems or questions, feel free to ask. Željko -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Upgrading anxiety
Pure and simple, try it out. Get a box that can run the latest code, and run it there. There's a problem, if you don't update production code and also test code to the latest version when they come out. I've seen this happen over and over again where no one is ready for the latest versions, and they're two, three or 8 years behind. This is an issue that you need to resolve and understand as part of the stories, there has to be a ci environment and team trying the latest code. That should be the same for production code and anything related to it, I'd posit that test code *is* the same asset. Cheers, Charley On Thu, Dec 29, 2011 at 3:34 PM, Lisa Crispin lisa.cris...@gmail.comwrote: We have Watir 1.6.2 and Ruby 1.8.6. We have MANY Watir/Test/Unit scripts which we (well, I) mainly use to help with exploratory testing, and to verify releases. I can't live without these scripts, so I don't want to break them. At the same time, I want to try the latest Watir and Webdriver to see if it correctly interprets the JS that our new Dojo code has - the version of Watir we have can't cope with it, and Canoo WebTest/HtmlUnit also cannot correctly interpret it. I perused the latest install instructions and info about the later Watir releases, and it sounds like our older Watir scripts aren't going to work with the later version? Is this true? How much effort is required to fix them? Is there a central location with this information that I just haven't found yet? If I install the latest Ruby and Watir/WebDriver, and our scripts don't work, can I back up to the old versions again? I only spend about 10% of my time doing any sort of coding, so though this might all be really obvious to y'all, it is something quite challenging and scary for me. I would hate to abandon Watir and the excellent scripts we have, but I don't get any support from my team on this. They are keen to try Selenium. Thanks, Lisa -- Lisa Crispin Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009) Contributor to _Beautiful Testing_ (O'Reilly 2009) http://lisacrispin.com @lisacrispin on Twitter http://entaggle.com/lisacrispin -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Upgrading anxiety
I've been playing with watir-webdriver. So far, I'm liking it but one thing that drove me a little batty was the behavior described here: http://watirmelon.com/2011/08/02/watir-webdriver-obselete-element-error/ And it does use 0-based indexing, which is a change from 1.6.2. I think the newer, non-webdriver versions of Watir also do 0-based indexing. From what I've seen so far it's pretty stable and it doesn't appear to have any problems with any of the pages I've been experimenting with. Is your team eager to try the older selenium or the new webdriver version? One possible argument for selenium-webdriver over the old selenium API is that the webdriver version of selenium supports multiple element selectors (e.g., :class='foo', :index=3). I don't think the old selenium API does that and am guessing that this is why xpath is so popular in the selenium world. If I had to use selenium I'd choose the webdriver API over the old API for that alone. And I think that the watir API has advantages over the selenium-webdriver API. Two things that struck me (please, someone correct me if I'm getting any of this wrong as I'm still in the process of comparison shopping and haven't done a lot with selenium): -The selenium-webdriver API doesn't seem to support getting collections and doing something with them (e.g., browser.tables.each...). -The selenium-webdriver API doesn't seem to support daisy-chaining elements. I don't think you can do something like browser.div(:class='foo', :id='bar').text_field(:id, 'baz').text. I've spent some time recently looking at the webdriver stuff and trying to figure out what the tradeoffs are. The new selenium API does seem a lot better than the older one. From: Lisa Crispin lisa.cris...@gmail.com To: watir-general@googlegroups.com Sent: Thursday, December 29, 2011 2:34 PM Subject: [wtr-general] Upgrading anxiety We have Watir 1.6.2 and Ruby 1.8.6. We have MANY Watir/Test/Unit scripts which we (well, I) mainly use to help with exploratory testing, and to verify releases. I can't live without these scripts, so I don't want to break them. At the same time, I want to try the latest Watir and Webdriver to see if it correctly interprets the JS that our new Dojo code has - the version of Watir we have can't cope with it, and Canoo WebTest/HtmlUnit also cannot correctly interpret it. I perused the latest install instructions and info about the later Watir releases, and it sounds like our older Watir scripts aren't going to work with the later version? Is this true? How much effort is required to fix them? Is there a central location with this information that I just haven't found yet? If I install the latest Ruby and Watir/WebDriver, and our scripts don't work, can I back up to the old versions again? I only spend about 10% of my time doing any sort of coding, so though this might all be really obvious to y'all, it is something quite challenging and scary for me. I would hate to abandon Watir and the excellent scripts we have, but I don't get any support from my team on this. They are keen to try Selenium. Thanks, Lisa -- Lisa Crispin Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009) Contributor to _Beautiful Testing_ (O'Reilly 2009) http://lisacrispin.com @lisacrispin on Twitter http://entaggle.com/lisacrispin -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
Re: [wtr-general] Upgrading anxiety
I think the only way you will now what the actual pain to upgrade to the newest version is is to actually upgrade. in saying that Why not make a clone of the current repository on a different machine or a VM install ruby on that vm(other machine) and all the gems you need and let her rip then try and figure out one by one whats broken :) on the watir-webdriver/selenium-webdriver differences I kind of look at it as watir just being one level of abstraction higher you can essentially do the exact same things in both just the watir layer makes it a bit easier and cleaner On Thu, Dec 29, 2011 at 4:48 PM, John Fitisoff jfitis...@yahoo.com wrote: I've been playing with watir-webdriver. So far, I'm liking it but one thing that drove me a little batty was the behavior described here: http://watirmelon.com/2011/08/02/watir-webdriver-obselete-element-error/ And it does use 0-based indexing, which is a change from 1.6.2. I think the newer, non-webdriver versions of Watir also do 0-based indexing. From what I've seen so far it's pretty stable and it doesn't appear to have any problems with any of the pages I've been experimenting with. Is your team eager to try the older selenium or the new webdriver version? One possible argument for selenium-webdriver over the old selenium API is that the webdriver version of selenium supports multiple element selectors (e.g., :class='foo', :index=3). I don't think the old selenium API does that and am guessing that this is why xpath is so popular in the selenium world. If I had to use selenium I'd choose the webdriver API over the old API for that alone. And I think that the watir API has advantages over the selenium-webdriver API. Two things that struck me (please, someone correct me if I'm getting any of this wrong as I'm still in the process of comparison shopping and haven't done a lot with selenium): -The selenium-webdriver API doesn't seem to support getting collections and doing something with them (e.g., browser.tables.each...). -The selenium-webdriver API doesn't seem to support daisy-chaining elements. I don't think you can do something like browser.div(:class='foo', :id='bar').text_field(:id, 'baz').text. I've spent some time recently looking at the webdriver stuff and trying to figure out what the tradeoffs are. The new selenium API does seem a lot better than the older one. -- *From:* Lisa Crispin lisa.cris...@gmail.com *To:* watir-general@googlegroups.com *Sent:* Thursday, December 29, 2011 2:34 PM *Subject:* [wtr-general] Upgrading anxiety We have Watir 1.6.2 and Ruby 1.8.6. We have MANY Watir/Test/Unit scripts which we (well, I) mainly use to help with exploratory testing, and to verify releases. I can't live without these scripts, so I don't want to break them. At the same time, I want to try the latest Watir and Webdriver to see if it correctly interprets the JS that our new Dojo code has - the version of Watir we have can't cope with it, and Canoo WebTest/HtmlUnit also cannot correctly interpret it. I perused the latest install instructions and info about the later Watir releases, and it sounds like our older Watir scripts aren't going to work with the later version? Is this true? How much effort is required to fix them? Is there a central location with this information that I just haven't found yet? If I install the latest Ruby and Watir/WebDriver, and our scripts don't work, can I back up to the old versions again? I only spend about 10% of my time doing any sort of coding, so though this might all be really obvious to y'all, it is something quite challenging and scary for me. I would hate to abandon Watir and the excellent scripts we have, but I don't get any support from my team on this. They are keen to try Selenium. Thanks, Lisa -- Lisa Crispin Co-author with Janet Gregory, _Agile Testing: A Practical Guide for Testers and Agile Teams_ (Addison-Wesley 2009) Contributor to _Beautiful Testing_ (O'Reilly 2009) http://lisacrispin.com @lisacrispin on Twitter http://entaggle.com/lisacrispin -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com
