We run our unit tests on every change. The results are posted here. http://watirbuild.com/
As Marek said, the issue being discussed is about packaging the unit tests, not getting them to pass. Bret Chuck vdL wrote: > > On Nov 7, 8:43 am, Bret Pettichord <[EMAIL PROTECTED]> wrote: > >> Comments inline. >> >> > <snip> > >>> CONCLUSION: >>> I would like to run tests after gems are installed. I think most users >>> want to do that so they can see watir in action. >>> >> Unfortunately this is not easy to fix right now. We are about half-way >> to the point of having a merged watir/firewatir testsuite, at which >> point the tests will be in the commonwatir module, not watir or >> firewatir. Would you like to help with this? I've found it to be much >> more time consuming than I originally expected. >> > > I realize there are 'good reasons' for this, but from the outside > persective of someone new to Watir, not having running unit tests > really gives a bad impression.. it makes people question if you are > really doing 'test first' development, and makes people wonder things > like 'how can they know this thing even works right if it's released > without unit tests in a running condition?" > > Do you really intend to release 1.6 (e.g. it's what gets installed if > someone does 'gem install watir' ) without unit tests working? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Watir General" group. To post to this group, send email to watir-general@googlegroups.com Before posting, please read the following guidelines: http://wiki.openqa.org/display/WTR/Support To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/watir-general -~----------~----~----~----~------~----~------~--~---
