S. Ranka et al. (Eds.): IC3 2010, Part II, CCIS 95, pp. 155–167, 2010. © Springer-Verlag Berlin Heidelberg 2010 A Novel Approach to Generate Test Cases Using Class and Sequence Diagrams Shireesh Asthana, Saurabh Tripathi, and Sandeep Kumar Singh Department of Computer Science and Information Technology Jaypee Institute of Information Technology A-10 Sector 62 Noida India {shireeshasthana2006,saurabhtripathijp}@gmail.com, sandeepk.singh@jiit.ac.in Abstract. It is very important in today's highly dynamic environment with changing requirements to develop test plan at each stage of the Software Devel- opment Life Cycle. Owing to the ever changing requirements, adequate updation in the requirement specifications is unavoidable. Due to lack of proper updation in the requirements, inconsistencies creep up. Research shows that number of software fail on account of these inconsistencies because proper test- ing is not possible on archaic requirements. Further, the increasing complexity of the projects make manual testing impossible. This calls for automatic testing of specifications to keep a check on the inconsistencies. Most of the earlier ap- proaches to testing specifications use intermediate forms that makes automation difficult. In this paper, we will present a novel approach to automatic test case generation that integrates information from UML class and sequence diagrams and at the same time does not use any intermediate form. Users input the dia- gram information in the form of XMI files. These files are processed to extract the environment variables from the class diagrams and test sequences from se- quence diagram and finally generate the test cases by applying Robustness Test- ing on the test sequence generated. Thus we avoid the intermediate forms as well as make automation an easier task. Keywords: Automatic Testing, Model Based Testing, Test Case Generation, UML, BVA, Robustness Testing. 1 Introduction With exponential increase in the complexity of industrial projects, there has been a ne- cessity for proper analysis and design of software before actual coding phase begins. With time, people have realized that softwares are not able to meet the requirements which are due to deficiency in the requirement analysis phase. Thus, from time to time, proper validation and testing of the specifications is required. But, with advent of bigger projects, it is impossible for people to manually test their specifications. This motivated us to build a tool which can automatically test the specifications of industry-level projects without the use of any intermediate form. Before moving on, let us give a brief introduc- tion on various models used for specifying requirements. Our tool is based on model