State Oriented Software System Testing for Object Oriented Applications using UML Diagrams
Keywords:SCOTEM, M(Message), Ob(Object)
Object-oriented software depends upon the successful integration of classes and object. When the classes are integrated to each other, there could be chance to arise several faults. The method in the area of research is SCOTEM (State Collaboration Test Model), based on UML collaboration and State chart diagrams. This is a state-based approach which generates the various test path based on the coverage criteria Selected and hence includes all the objects states in collaboration.
In this paper the analysis of SCOTEM model is done for a case study using a prototype tool developed in C language. Various Mutants are analyzed by using this prototype tool. The results show that the related technique effectively detects all the seeded faults when complying with the most demanding adequacy criterion and still achieves reasonably good results for less expensive adequacy criteria.
2. Zhao R, Lin L. An UML State chart Diagram-Based MM-Path Generation Approach for Object-Oriented Integration Testing. World Academy of Science, Engineering and Technology, International Journal of Computer and Systems Engineering 2008; 2(10): 3470-5.
3. labiche Y, P.thevenod-Fosse, Waeselynck H et al.Testing Levels for Object-oriented Software. 2000 in ICSE, 2300 1-58113-206-9/00/06.
4. Bruegge B, Dutoit AH. Object-Oriented Software Engineering: Using UML, Patterns and Java, Prentice Hall, Second Edition, 2003.
5. Baldini A, Benso A, Prinetto P. System-level Functional Testing from UML Specifications in End-of-production Industrial Environments. International Journal of Software Tools Technology and Transfer 2004; 7(4): 326-340.
6. Briand L, Labiche Y, Wang Y. An Investigation of Graph- Based Class Integration Test Order Strategies, IEEE Transactions on Software Engineering 2003; 29(6): 594 - 607.
7. Briand LC, Di Penta M, Labiche Y. Assessing and Improving State-Based Class Testing: A Series of Experiments. IEEE Transactions on Software Engineering 2004; 30(11): 770-79.