UML Activity Diagram Use for Functional Test Suit Generation and Redundancy Removal Supported Model Driven Testing
Runal G.1, Pramod Jadhav2, Pruthviraj R. Pawar3
1Runal G., IT Department, Bharati Vidyapeeth Deemed to be University College of Engineering, Pune, India.
2Prof. Pramod Jadhav, IT Department, Bharati Vidyapeeth Deemed to be University College of Engineering, Pune, India.
3Prof. Pruthviraj R. Pawar, Computer Department, Bharati Vidyapeeth College of Engineering, Navi Mumbai, India.
Manuscript received on July 20, 2019. | Revised Manuscript received on August 10, 2019. | Manuscript published on August 30, 2019. | PP: 2391-2397 | Volume-8 Issue-6, August 2019. | Retrieval Number: F8370088619/2019©BEIESP | DOI: 10.35940/ijeat.F8370.088619
Open Access | Ethics and Policies | Cite | Mendeley
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
Abstract: The method mixes up the extended finite state machine & UML activity diagram to generate the test model. H good coverage of test of all probable scenarios. Here an activity diagram describes the operation of the system, decision ere we have considered different coverage criteria for generating the test paths from the model for node transition from one action state to another. Also flow of control is represented. These will emphasis on sequence and condition of flow. It also gives idea about internal nodes. Refactoring is the process of altering an application’s source code of its external behavior is not changing. The purpose of code refactoring is to improve some of the nonfunctional properties of the code, such as readability, complexity, maintainability and extensibility. Refactoring can extend the life of source code, preventing it from becoming legacy code. The refactoring process makes future enhancements to such code a more pleasant experience. Refactoring is also known as reengineering. Test cases tend to be massive in range as redundant take a look at cases square measure generated because of the presence of code smells, thus the requirement to scale back these smells. Methods Statistical Analysis: This analysis adopts a proactive approach of reducing action at laws by police investigation the lazy category code smells supported the cohesion and dependency of the code and applying the inline category refactoring practices before take a look at case generation there by considerably avoiding redundant take a look at cases from being generated.
Keywords: UML, sequence diagram, depth first search algorithm, software testing, test case generator, refactoring, redundancy test case.