Basically, the book recommends that you test everything. The book goes on to recommend that if you later find any bugs that need to be fixed, that the fix also include yet more tests to ensure that the bug is and stays fixed. They really mean "ruthless" testing.
The book is worth adding to your personal bookshelf. cheers, - Michael On Mon, Jun 14, 2010 at 8:30 PM, Christopher Schnell <ty...@mda.ch> wrote: > Thanks for the suggestion. Until my boss orders this book, could you give > me a short answer ? > > > > Just curious J > > > > Regards, > > Christopher. > > > > *Von:* symfony-users@googlegroups.com [mailto: > symfony-us...@googlegroups.com] *Im Auftrag von *Michael Hodges > *Gesendet:* Montag, 14. Juni 2010 19:56 > *An:* symfony-users@googlegroups.com > *Betreff:* Re: [symfony-users] Functional tests for Form validators? > > > "The Pragmatic Programmer: From Journeyman to Master" by Andrew Hunt and > David Thomas labels their chapter on this topic "Ruthless Testing" which > suggests one answer to your question. It's an excellent book. > > - Michael > > On Mon, Jun 14, 2010 at 4:12 AM, Christopher Schnell <ty...@mda.ch> wrote: > > Hi all, > > > > As I am writing lots of functional tests these days, I was wondering if one > should test the standard validators of a form. > > > > Let’s say, we have a „change Password“ form. This simple form with three > fields would require lots of tests, for example > > · Is the current password correct ? > > · Is the new passwort long enough > > · Is the new password entered twice > > · … > > > > Now all these „tests“ are implemented with standard validators. Would it be > just lazy not to test these cases? > > > > How many tests do you write for such things? > > > > Thanks and regards, > > Christopher. > > > > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > > > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony users" group. > To post to this group, send email to symfony-users@googlegroups.com > To unsubscribe from this group, send email to > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/symfony-users?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en