Test Case Generation using UML Activity Diagram & Composite Structure Diagram

In software development, Quality is an important thing. We get the best quality of software when we test it properly. In present day the size and complexity in object oriented software are increased , Due to this manual testing become very resource consuming and not able to provide proper results. To handle this we need automatic test case generation which helps in finding the errors and bugs. Test cases we generate in design phase only, which is very early in software development process. We use unified modelling language (UML) to visualise the designs and structure of object-oriented software. From UML diagram, we generate efficient test cases which gives proper results during testing. We first focus on the generation of test cases from the Activity diagram. Activity Diagrams are used to describe the behaviour of the models i.e. dynamic aspects of model. In activity diagram we describe the flow of activity from one to another. Every activity represents a different operation. We first use Rational Software Architect (RSA) to develop the Activity Diagram. From here we generate XMI (XML metadata interchange). We generate the intermediate graph by parsing the XMI code automatically. After developing the intermediate graph , by using it, in our proposed algorithm topdown test case generation algorithm we generate test cases. The generated test cases are used in testing to find out the errors, by removing erros we increase the quality of the software. In our next work, we focus on the UML composite structure diagram (CSD). CSD defines the interaction between components because of this we use these generated test scenarios in the integration testing. We first use Rational Software Architect (RSA) to develop the CSD. From here we generate XMI (XML metadata interchange). We generate the intermediate graph by parsing the XMI code automatically. By using intermediate graph, in our algorithm we generate test scenarios. The generated test scenarios are used in integration testing to find out the errors