| || |
Object oriented testing??
How do I go about with Object Oriented testing?
I am supposed to test C++ classes where dependecy is the major issue. Can anyone tell me how do I go about to test these classes?
Re: Object oriented testing??
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by coolvj2:
How do I go about with Object Oriented testing?<HR></BLOCKQUOTE>
I assume you mean this in the general sense and not in the strict sense of Shel Siegel. If you do mean the latter sense, I highly recommend the book Object Oriented Software Testing: A Hierarchical Approach by Shel Siegel. It is a little high-level in some places but worth the read for a strict object-oriented testing regime. Another really good book is Testing Object-Oriented Software by David Kung.
There are many different viewpoints about how object-oriented testing should be done from the standard unit test approaches that we all know and love to more in-depth methods. A good bibliography of materal is found here: http://www.rbsc.com/pages/ootbib.html
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>I am supposed to test C++ classes where dependecy is the major issue. Can anyone tell me how do I go about to test these classes?<HR></BLOCKQUOTE>
Dependency is usually the major issue with C++ classes no matter what. In general, however, it sounds like you are talking about unit testing. The way I like to unit test C++ classes is by adapting data flow techiques to the object-oriented role of the language. This breaks your test cases up into four specific categories:
Testing the definition-use paths of a class variable within a single method in the class.
Inter-Method: Testing the definition-use paths of a class variable by methods of a class that are called by a single public method.
Intra-Class: Testing the definition-use paths of the class variable across public method calls of a single class.
Inter-Class: Testing the definition-use paths of the class variables across method calls of several classes.
(By the way, these are not my designations. I am not sure who came up with them but they are out there in the literature.) Also, there are entities called Decision Logic Tables that can model the relations among equivalence classes can be used to design test cases for relationships among object classes in C++.
As far as what you should strictly do, it would depend on the nature of the dependencies you are talking about and it would also depend on how much you already know about unit testing techniques.