Automated testing of database classesby MrCromeDome (Deacon)
|on Dec 27, 2004 at 15:44 UTC
MrCromeDome has asked for the wisdom of the Perl Monks concerning the following question:
Some time ago, I took the plunge and started to implement auotmated testing of my web applications. I have to admit it's been pretty cool :) Testing has already helped me to uncover problems and inconsistencies with my application's API, and has also helped me uncover and diagnose some really subtle bugs in our applications. Lately, I've been implementing a number of database classes in Class::DBI, and I'm having some difficulty determining what kinds of tests I want to implement, or even should be implementing. I've written test suites for a couple of my classes, and sadly, they look more like test suites for Class::DBI than anything of use to my application. It seems like duplicated effort to me, as Class::DBI comes with its own series of tests.
In the end, my application will have a number of classes, but they will be fall into one of two groups: those that view and update data, and those that only view data. I'm not sure what kinds of tests I should be writing for these instances though. Does anyone have any suggestions for what I can do to test my database classes? For those of you who have implemented testing of database classes, what things have you tested?As always, thank you for your time and insight!