Jayant et al., International Journal of Advanced Research in Computer Science and Software Engineering 4(2), February- 2014, pp.

Transcription

1 Volume 4, Issue 2, February 2014 ISSN: X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: Special Issue: International Conference on Advanced Developments in Engineering and Technology Conference Held in Lord Krishna College of Engineering Ghaziabad, India An Approach of Software Design Testing Based on UML Diagrams K. P. Jayant 1, Renu Garg 2, Vinod Kumar 3, Prof. Ajaya Rana 4 Abstract: Software testing is one of the most required phase in software development life cycle (SDLC) for successful execution of software / computer applications. The failure of software without proper testing is very high. Therefore software testing is required more attention to avoid the arbitrary failure or crashes of software product in SDLC. Regression testing of software is the process of verification that previously functioning of software are remains after the changes. In this paper we have done systematic review of empirical evaluations of regression testing techniques and test case generation based on UML research papers. These papers were published in major software engineering journals and conferences. Our study from various research papers has concluded that no ideal solution for software design testing exists through the UML diagrams, except for small group of techniques. We have proposed an empirical solution in this area. It is required to carefully consider the context carefully in which our studies are being taken place. Index Terms: software testing, test case, comparisons, verification,, Test case selection, Test case minimization, UML. I. INTRODUCTION Software testing performs an important role during software design, development and release. Regression testing is required factor for proper testing of software. Efficient regression testing [1] is important for organizations with a large share of their cost in software development. It involves determining which test cases need to be re-executed in order to verify the behavior of modified software. In the success of software, regression testing process required high cost and more time for the complex software system. Research efforts on finding cost efficient techniques and methods for regression testing is exists on variety of topics- such that test case selection based on code changes [1, 15, 14, 27] and specification changes [31], evaluation of selection techniques, change impact analysis [8][6], regression tests for different applications e.g. on database application [16], regression testing of GUIs and test automation [25], and test process enhancement [34]. These techniques emphasized on the code based analysis of regression test selection. Other factor of comparative analysis is based on UML design. In this paper we have reviewed the different aspects of software testing. We have proposed an idea to test software at early stage with the help of Unified Modeling Language (UML). The paper summarized in five sections. Section-2 described the UML & testing. Section-3 elaborates related work of our research work, in section-4 described a proposed approach, section-5 we have mentioned result and discussion, and the section-6 we have written conclusion of work. II. THE UML The UML is a visual modeling language and used for visualize, specify, construct and document the artifacts of a software system [32]. The major area of UML views: Structural, Dynamic and Model Management [30]. Structural view includes class diagram, use case diagram, component diagrams and deployment diagrams. Dynamic view considered statechart diagram, activity diagram, sequence diagram and collaboration diagram. Model management view includes class diagram [30]. Class diagrams - class structure and associations component diagrams- map classes to software unit deployment diagrams - physical system structure. The behavioral elements includes: Use Case Diagrams - functionality as seen by actors, Interaction Diagrams - object message sequences, Activity Diagrams - business / software processes, State Diagrams - object state transition behavior A. UML Based Software Testing UML activity diagram is a notation suitable to modeling a concurrent system in which multiple objects interact with each other. Kim [5] proposes a method to generate test cases from UML activity diagrams that minimizes the number of test cases generated while deriving all practically useful test cases. This method first builds an I/O explicit Activity Diagram from an ordinary UML activity diagram and then transforms it to a directed graph, from which test cases for the initial activity diagram are derived. 2014, Lord Krishna College of Engineering Ghaziabad, India Page 148

2 P.Samuel et al [6] considered the feature of UML 2.0 sequence diagrams to generate message sequences and an intermediate representation of the sequence diagram is built, which is called the Sequence Dependency Graph (SDG). The message sequences are incorporated into the SDG. They had used a traversal algorithm to generate test sequence from SDG. Stefania Gnesi, [37] propose a formal conformance testing relation for input-enabled transition systems with transitions labeled by input/output-pairs (IOLTSs). IOLTSs provide a suitable semantic model for a behavioral subset of UMLSCs. They had provided an algorithm which, for a UMLSC specification and the alphabet of implementations, generates a test suite. The algorithm is proven exhaustive and sound w.r.t. the conformance relation. Waldemar Pires [39] had proposed a fully automated technique to perform conformance checking of Java implementations against UML class diagrams. In their approach, reused the Design Wizard Java API that allows us to write design rules as JUnit tests, i.e., to write them as code directly in the programming language. Several experiments on simple scenarios, Simple designs involving classes, associations, inheritance have been checked. Advantage of approach lies in the fact that we automatically generate design tests from UML class diagrams to Java code that play the dual role of design test and implementation language. UML diagrams, specifically class diagrams, are widely used in various software development processes; therefore, approach may be used in these processes to check the conformance between design and implementation. Graves et al. [17] categorized the regression test selection techniques as: Minimization Techniques : These techniques focus on selectively retest the software with minimum test cases covering modified or affected portions. Dataflow Techniques: These techniques select those test cases, which execute data interactions that have adverse effect by changes made. Safe Techniques: These techniques are designed to reveal the same faults as a retest-all strategy reveals. Thus, those test cases that exercise the suspected portion having faults are more focused because they can reveal other most likely faults and exercise the critical functionality. Ad-Hoc /Random Techniques: These techniques build regression test suite by choosing randomly test cases from original test suite. Randomly rerunning test cases do not address the coverage of affected portions and may not find the most severe faults. Retest-All Techniques: These techniques rerun the entire original test suites to ensure that modifications have not regress the software functionality, but this requires enough time or resources to rerun the entire test suites. III. RELATED WORK A. Briand L. et al [3][5], had presented a methodology and a tool to support test selection from regression test suites based on change analysis in object-oriented design. Test case is classified as: Obsolete - A test case that cannot be executed on the new version of the system or Re-testable: A test case is still valid but needs to be rerun for the regression testing to be safe or Reusable: A test case that is still valid but needs not to be rerun to ensure regression testing is safe. Authors had discussed changes in three types of UML Diagrams: class diagrams, sequence diagrams and use case diagrams. It has been described in two versions of class diagram their added/deleted attributes, changed attributes and added/deleted methods, changed methods through UML class diagram. Changes between two versions of the same sequence diagram compare added / deleted use cases and changed use cases. A regression test selection tool (RTS Tool) has been developed based on design changes. B. Fahad M. et al [23] described theoretically advantages and drawbacks of using UML based regression testing. UML model helps in identifying changes for regression test selection effectively. Regression testing can be applied at any level of testing i.e. unit testing, integration testing, and system level testing. UML design for regression testing has certain advantages over code based regression testing. Author had highlighted advantages and significance of using UML design versus code for regression testing. Traceability, scalability, language dependence, cost, executable UML, complexity are advantage over code based regression testing. UML based regression testing techniques have some drawbacks as invisible changes, consistent and up-to-date design, low precision. C. Kim H. et al [18][23], A method had proposed it generates test cases from UML activity diagrams that minimizes the number of test cases generated while deriving all practically useful test cases. In their introduction they had described that the activity diagram is a suitable modeling language for describing the interactions between system objects. Activity diagram can be conveniently used to capture business processes, workflows and interaction scenarios. They had proposed a method that is based on an I/O explicit Activity Diagram (IOAD) model, which is an abstraction model obtained from the fully expanded activity diagram by exposing only external inputs and outputs. Major limitation of their method is that it is not generalized and there is no fixed method to IOAD test case generation. D. Wang. L. et al [40][21], described test case generation based on UML activity diagram. Their method generates test cases from activity diagrams, which modifies Depth First Algorithm (DFS) for automated tests generation. The deficiency of this paper is that any fork node has only two exit edges; these assumptions limit the applicable scope of the proposed algorithm. Basic paths can be found by the DFS algorithm, while the detailed walkthrough of the proposed algorithm shows that some test scenarios are not generated, especially when the test scenarios are derived from the forkjoin parts of the activity diagram. In this paper two techniques are used table representation and DFS algorithm. Using simple fork-join is limitation of this paper. IV. PROPOSED TECHNIQUE Our approach checks the functionality of software at design level, which can reduce time and effort during testing activity. Test cases will be generated from the UML based design specifications. Test case generation based on code 2014, Lord Krishna College of Engineering Ghaziabad, India Page 149

3 further becomes difficult due to individual style of code writing. It is proposed that test cases should be derived from design specifications. It is proposed to use globally accepted modeling standards, UML diagrams and their specifications to generate test cases. Various UML diagrams can be used to identify any changes in design and based on this identified change, regression test can be derived. The Unified Modeling Language (UML) is a standard visual modeling language that is designed to specify, visualize, construct and document the artifacts of software systems. UML diagrams can be considered as the means to generate test cases. Instead of deriving test cases from the UML diagrams directly, our approach selects the test cases from the set of the generated test cases according to a given UML specifications. In proposed approach, regression test cases will be generated from the design code available in petal files / mdl file. UML Class Diagram Text file (petal file) Extracted Data from petal file Test Cases Fig 1: Process flow for notations extraction and test case generation V. RESULT: DATA EXTRACTION FROM UML Class diagrams describe the structure of the classes. The use of class diagrams shows the existence of classes and their relationship in the logical view of a system. Fig-2 shows the student information system.class (student department and course ) is define with their name,attributes and operations Fig-2 Class diagram for student info system 2014, Lord Krishna College of Engineering Ghaziabad, India Page 150

4 The class diagram converted into a mdl file format.... root_usecase_package (object Class_Category "Use Case View" quid "4CF77CFE006F" exportcontrol "Public" global TRUE logical_models (list unit_reference_list) logical_presentations (list unit_reference_list (object UseCaseDiagram "Main" quid "4CF77CFE03AA" root_category (object Class_Category "Logical View" quid "4CF77CFE006E" exportcontrol "Public" global TRUE subsystem "Component View" quidu "4CF77CFE0070" logical_models (list unit_reference_list (object Class "Student" quid "4CF77E0E02FD" used_nodes (list uses_relationship_list (object Uses_Relationship quid "4D04212D032C" supplier "Logical View::Department" quidu "4CF77E2D0128")) operations (list Operations (object Operation "Search" quid "4CF77EDB0000" concurrency "Sequential" opexportcontrol "Public" Fig-3 mdl file for Fig-2 Basically it describes class s objects, relationship with the individual identification numbers. Extracted data of class diagram and their relationship from text file and displayed into form for test case plan as in the figure -4 shown. Fig-4 Extraction of class and relationship from mdl text file VI. CONCLUSION Software testing is process of executing software in a controlled manner and where regression testing is an expensive but necessary maintenance activity performed on modified software to provide confidence that changes are correct and do not adversely affects other portions of the software. In this paper we have proposed an approach to extract data from UML diagram and use for test case plans. 2014, Lord Krishna College of Engineering Ghaziabad, India Page 151

5 References: [1] Agrawal, H., Horgan, J.R., Krauser, E.W., and London, S.A Incremental regression testing. In Proceedings Conference on Software Maintenance CSM-93 (Cat. No.93CH3360-5). IEEE Comput. Soc. Press, [2] Ali, S.,et al A State-based Approach to Integration Testing based on UML Models. Carleton Technical Report SCE-05-02, Version 3, October 2006 [3] Briand L. C., Labiche Y. and Soccar G., Automating Impact Analysis and Regression Test Selection Base on UML Designs, Proc. IEEE International Conference on Software Maintenance (ICSM), Montreal (Canada), IEEE Computer Society, pp , October 3-6, [4] Briand L. C., Labiche Y. and O'Sullivan L., Impact Analysis and Change Management of UML Models, Carleton University, Technical Report SCE-03-01, February, [5] Briand L., Labiche Y., Soccar G.. Automating impact analysis and regression test selection base on uml designs, technical report, carleton university, sce-02-04, version 2, August [6] Briand L., Y. Labiche, Sullivan L. O, and Owka M. S. Automated Impact Analysis of UML Models. Journal of Systems and Software, 79(3): , [7] Briand L.C. and Y. Labiche. A UML-Based Approach to System Testing. In Proceedings of 4th International Conference UML The Unified Modeling Language: Modeling Languages, Concepts, and Tools, volume 2185, pages Springer-Verlag Lecture Notes In Computer Science, [8] Briand L.C., Labiche Y., Soccar G., Automating Impact Analysis & Regression Test Selection Based on UML Designs, Proc. of Intl. Conference on Software Maintenance, IEEE,2002. [9] Briand,L.C, Labiche,Y, Yue, T, Automated Traceability Analysis for UML Model Refinements, Technical Report: TR SCE-06-06, Version 2, Carleton University, Department SCE Software Quality Engineering Laboratory 1125 Colonel By Drive, Ottawa, ON K1S5B6, Canada, August [10] Chen Yanping et al, Model-based Regression Test Suite Generation Using Dependence Analysis, AMOST'07, London, UK,ACM, Pg.No ,July 9-12, 2007 [11] Debasish Kundu and Debasis Samanta, A Novel Approach to Generate Test Cases from UML activity diagram chair of software engineering ETH Zurich,Vol.8, No.3, May-June 2009 [12] Deng D., et al Model-based Testing and Maintenance, Proceedings of the IEEE Sixth (ISMSE 04),pg. 1-8, 2004 [13] Fahad M. and Nadeem A., A Survey of UML Based Regression Testing, In IFIP International Federation for Information Processing, Volume 288; Intelligent Information Processing IV; Zhongzhi Shi, E. Mercier-Laurent, D. Leake; (Boston: Springer), pp ,2008 [14] Farooq Q. M.Z.Z. Iqbal, Z.I. Malik, A. Nadeem, An approach for selective state machine based regression testing, Proceeding of AMOST 07, July 2007, UK, pp , ACM. [15] Fischer, K., Raji, F., and Chruscicki, A A methodology for retesting modified software. In NTC '81. IEEE 1981 National Telecommunications Conference. Innovative Telecommunications - Key to the Future. IEEE, 6-3. [16] Haftmann, F., Kossmann, D., and Lo, E A framework for efficient regression tests on database applications. VLDB Journal. 16(1), [17] Graves T. L., Harrold M.J., Kim J., Porter A., and Rothermel G., An Empirical Study of Regression Test Selection Techniques, ACM Transactions on Software Engineering and Methodology, Vol. 10 (2001), No. 2, pp [18] Kim H. [14], Kang S., Baik J., I. Ko, Test Cases Generation from UML Activity Diagrams,8th ACIS International Conference on Software Engineering,Artificial Intelligence, Networking and Parallel/ Distributed Computing(ACIS-SNPD), IEEE Computer Society, July [19] L. Briand and Y. Labiche, A UML-based approach to system testing, Journal of Software and Systems modeling 1 (1), 2002, pp [20] Leila Naslavsky, Hadar Ziv Debra, J. Richardson, A Model-Based Regression Test Selection Technique, Proc. ICSM 2009, Edmonton, Canada, IEEE, pg No [21] Liu M. et al, Design of Testing Scenario Generation Based on UML Activity Diagram, 12: , [22] M. Liu, M. Jin, and C. Liu. Design of Testing Scenario Generation Based on UML Activity Diagram. The Engineering and Application of Computer(inChinese), 12: , [23] M.S.Lund and K. Stolen, Deriving Tests from UML 2.0 Sequence Diagrams with neg and assert, AST 06, May [24] Mansour N., and Takkoush H., UML based regression testing for OO software, Proc. Of 11th IASTED conference software engineering and applications. Nov, Cambridge, USA. [25] Memon, A.M Using tasks to automate regression testing of GUIs. In IASTED International Conference on Artificial Intelligence and Applications - AIA ACTA Press, [26] Mingsong C. and Xiaokang Q. and Xuandong L., Automatic Test Case Generation for UML Activity Diagrams, International Conference on Software Engineering, Proceedings of the 2006 International workshop on Automation of Software Test, ACM, May [27] Pei, H., Xiaolin, L., Kung, D.C., Chih-Tung, H., Liang, L.,Toyoshima, Y., and Chen, C A technique for the selective revalidation of OO software. Journal of Software Maintenance: Research and Practice. 9(4), , Lord Krishna College of Engineering Ghaziabad, India Page 152

6 [28] Pilskalns O., Uyan G., Andrews A., Regressin Testing UML Designs, 22nd IEEE international Conference on software maintenance (ICSM 2006). [29] [6] P.Samuel et al, Test Sequence Generation from UML Sequence Diagrams, Ninth ACIS International Conference on Software Engineering,IEEE-2008, pg [30] Rumbaugh, Jacobson, and Booch. The Unified Modeling Language Reference Manual. Addison-Wesley, Reading, MA, [31] Sajeev, A.S.M. and Wibowo, B Regression test selection based on version changes of components. In Tenth Asia-Pacific Software Engineering Conference. IEEE Comput.Soc, [32] Sparx s., UML Tutorials [33] Samuel Philip, Joseph Anju Teresa, Test Sequence Generation from UML Sequence Diagrams, ACIS International Conference on Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing, pg , IEEE, 2008 [34] Stallbaum H., et al An Automated Technique for Risk-based Test Case Generation and Prioritization, Leipzig, Germany, AST 08, May 11, 2008 [35] Supaporn Kansomkeat and Wanchai Rivepiboon, Automated-Generating Test Case Using UML State chart Diagrams Proceedings of SAICSIT, Pages , 2003 [36] Supaporn Kansomkeat et al, A comparative evaluation of tests generated from different UML diagrams, pg , IEEE, 2008 [37] Stefania Gnesi, Formal Test-case Generation for UML Statecharts EU-IST IST (AGILE) and MIUR/SP4. [38] Vokolos, F.I. and Frankl, P.G Pythia: a regression test selection tool based on textual differencing. In Reliability, Quality and Safety of Software-Intensive Systems. IFIP TC5 WG5.4 3rd International Conference. Chapman & Hall, [39] Waldemar Pires, UMLbased Design Test Generation SAC 08 March 1620, 2008, [40] Wang. L., Yuan, J., Yu, X.,, Hu, J., Li, X., Zheng G., Generating Test Cases from UML Activity Diagram based on Gray-Box Method, National Natural Science Foundation of China, Author-1 : Dr. K.P. Jayant, MCA, M.Tech (IT), Ph.D. (CS), Working as Senior Associate Professor in department of Computer Application at ABES Engineering College. Author-2 : Mr. Vinod Kumar, MCA, M.Tech(CSE) working as Associate Professor, Department of Computer Application at ABES Engineering College, Ghaziabad Author-3 : Ms. Renu Garg, MCA, M.Tech (CSE), working as Associate Professor in Department of Computer Application at ABES Engineering College, Ghaziabad. 2014, Lord Krishna College of Engineering Ghaziabad, India Page 153