How do you test?
by Dejan Bosanac
write test, write code, refactor
and that was the point were all further discussion stopped. Of course, this is only the introduction to this topic as there are many other factors that should be considered in order to deliver quality software to your customers.
Finally, in past few months I ran across few articles (and blog entries) that broadens discussion on this very important topic. In this post I'll collect them in one place and summarize their content hoping that they will be a valuable read to you (as they were to me).
|Bart van Kuik
|I find maintenance of tests can take quite a bit of time and is boring, too. I keep the amount of test code small. So what I'm currently doing on my project at work is testing the modules (yes modules, I do Perl), but not the GUI. Also, I don't put in a lot of strange input. I definitely wouldn't call it 'heavily tested', but it suits me for now.|
I test what I need when I need. I have done a lot of Automated Gui Testing and do code tests (unit) when & where needed, when and if time allows. Regretfully, some customer projects do not allow even the smallest tribute of time for testing. Some barely had time to quickly slap the code together and pray. Then it really just gets on-the-spot tests, and in the maintence phase tests will be done on errors. Not the best situation but what you have to do when time is tight.
|Since you mentioned defensive programming I was surprised you didn't mention assertions and logging as a way to catch errors in code rapidly during and after development.|
How I can change avatar in this forum?