On 16 sep, 02:23, Ben <benzhe...@gmail.com> wrote:
> Thanks, Thomas. I will try it out and it seems that writing unit tests
> costs a lot of time.
It depends how many tests you write (racing for 100% code coverage is
counter productive); but in the end, it really *saves* you a lot of
time (prevents regressions, etc.) (investment cost vs. maintenance
cost)
I can tell you that because we have a project with absolutely *no*
automated test, and we regularly broke something while fixing another
or adding a new feature (this was also made far easier because we had
spaghetti code all around the place, and no clear specification to
start with)
Good literature can be found at: http://googletesting.blogspot.com/
(remember to read their TotT category ;-) )
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
