RSS Feed (xml)
Recently asked on the OTN PL/SQL forum:
I am reading a book: Learning Oracle PL/SQL by Bill Pribyl and Steven Feuerstein.
I am a newbie of PL/SQL and I got no other programming XPs. but in the very first of this book they are introducing something called: testing, to make some test programms /utilites.
I found that is very hard to make, is it neccessary?
Apparently, after you've typed the final semicolon, you can either sit back and open a beer with the satisfaction of a job well done, or you can check whether the thing works. And apparently it's hard, so, do we really have to?
Well, another poster was recently arguing that PL/SQL is not suited to unit testing anyway, or refactoring either for that matter, because it isn't object oriented. I think that will be my excuse from now on. You want me to test stuff, go make PL/SQL more objecty.
1 comment:
Chinchu,
Unit testing has nothing to do with being object oriented or not. You can and should and must test with any language in which you program.
OO languages probably offer some advantages when it comes to testing, such as mock objects, but you can do very fine testing in PL/SQL.
I suggest you check out the open source utPLSQL (analogous to Junit) and the much more powerful commercial product, Quest Code Tester for Oracle (I was the original designer and implementer of both).
Code Tester is my main focus today and it offers the best test automation of any PL/SQL tool.
Regards,
Steven Feuerstein
www.ToadWorld.com/SF
Post a Comment