I'm looking forward for that too :) Here is my current action plan: 1) Run watirspec against watir with ruby 1.9.3 2) Add more guards if they make sense OR implement watir code to make the spec pass
I'm having currently 175 failures out of 1003. Since Watir doesn't conform to the API of WatirSpec in full extent then i have to do changes which are not backwards compatible. Having that and Semantic Versioning ( http://semver.org/) in mind, i'd say that the next version number for Watir should be 3.0. I'd also suggest to delete current unit tests for Watir when specs are passing, because it could take some time to change these tests to pass after all changes due to incompatibilities and having them around doesn't make much sense. I think if there should be watir specific tests then these could be done by using RSpec also. And when it comes to 3.1 then one idea would be to remove firewatir and commonwatir code so there would be only watir gem. Anyone knows who holds the username "watir" in github currently? I guess having compatibility between Watir-WebDriver is worth these changes. What do you guys think? Jarmo On Thu, Dec 8, 2011 at 12:53 PM, Željko Filipin < zeljko.fili...@wa-research.ch> wrote: > On Thu, Dec 8, 2011 at 12:08 AM, Jari Bakken <jari.bak...@gmail.com> > wrote: > > Jarmo now has push access to the watirspec repo. > > Congratulations Jarmo. I am looking forward to seeing watir gem having > good results with watirspec. > > Željko > -- > watir.com/book - author > > _______________________________________________ > Wtr-development mailing list > Wtr-development@rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development >
_______________________________________________ Wtr-development mailing list Wtr-development@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development
