I'm a firm believer that tests should not be flaky - a failure means you broke something, a pass means your code works.
With the HTML and JS as it is right now I'm not confident that I could write selenium tests that would not give me more false results than true ones. On Wed, Oct 12, 2011 at 4:35 PM, Michael Gall <[email protected]> wrote: > Notably not on this list is unit or integration testing. The code is not at >> the point where this can be performed effectively. >> > > This seems crazy. I can definitely understand the unit testing, but writing > some Selenium tests before you start making any changes is a great way of > creating a nice little safety belt for yourself. > > Cheers, > > > Michael > > > -- > Checkout my new website: http://myachinghead.net > http://wakeless.net > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- Michael Pearson The Bon Scotts; http://www.thebonscotts.com -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
