Open AccessUML Activity Diagram Use for Functional Test Suit Generation and Redundancy Removal Supported Model Driven Testing
Author(s) -
Runal G.*,
Prof. Prajakta B. Jadhav,
Priyanka R. Pawar
Publication year - 2019
Publication title -
international journal of engineering and advanced technology
Language(s) - English
Resource type - Journals
ISSN - 2249-8958
DOI - 10.35940/ijeat.f8370.088619
Subject(s) - code refactoring , computer science , maintainability , programming language , activity diagram , unified modeling language , cohesion (chemistry) , test case , redundancy (engineering) , source code , code (set theory) , software engineering , software , chemistry , regression analysis , organic chemistry , machine learning , operating system , set (abstract data type)
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.