【正文】 s are event contexts are not incorporated and need coverage and test adequacy criteria to check how these impacts fault detection. Figure 3. Automated Test Case Generation 3. REPAIRING TEST SUITES Si Huang et al [6], proposed a method to repair GUI test suites using Geic algorithm. New test cases are generated that are feasible and Geic algorithm is used to develop test cases that provide additional test suite coverage by removing infeasible test cases and inserting new feasible test cases. A framework is used to automatically repair infeasible test cases. A graph model such as EFG, EIG, ESIG and the ripped GUI structure are used as input. The main controller passes these inputs to the test case assembler which then passes the ESIG model to the covering array generator along with the strength of testing. This covering array generator generates an initial set of event sequences. The covering array information is send to test case assembler and it assembles this into concrete test cases. These are passed back to the controller and test suite repair phase begins. Feasible test cases are returned by the framework once the repair phase is plete. Geic algorithm is used as a repair algorithm. An initial set of test cases are executed and if there is no infeasible test cases, it exits and is done. If infeasible test cases are present, it then begins the repair phase. A certain number of iterations are set based on an estimate of how large the repaired test suite will be allowed to grow and for each iteration the geic algorithm is executed. The algorithm adds best test case to the final test suites. Stopping criteria’s are used to stop the iterations. The advantages are it generates smaller test suites with better coverage on the longer test sequences. It provides feasible test cases. But it is not scalable for larger applications as execution time is high. As GUI ripping is used, the programs that contain event dependencies may not be discovered. 4. GUI TESTING ON VARIOUS APPLICATIONS . Industrial Graphical User Interface Systems Penelope Brooks et al [7], developed GUI testing methods that are relevant to industry applications that improve the overall quality of GUI testing by characterizing GUI systems using data collected from defects detected to assist testers and researchers in developing more effective test strategies. In this method, defects are classified based on beizer’s defect taxonomy. Eight levels of categories are present each describing specific defects such as functional defects, functionality as implemented, structural defects, data defects, implementation defects, integration defects, system defects and test defects. The categories can be modified and added according to the need. If any failures occur, it is analyzed under which defect category it es and this classification is used to design better test oracle to detect such failures, better test case algorithm may be designed and better fault seeding models may be designed. Goal Question Metric (GQM) Paradigm is used. It is used to analyze the test cases, defects and source metrics from the tester / researcher point of view in the context of industrydeveloped GUI software. The limitations are, the GUI systems are characterized based on system events only. User Interactions are not included. . CommunityDriven Open Source GUI Applications Qing Xie and Atif M. Memon [8], presented a new approach for continuous integration testing of webbased munitydriven GUIbased Open Source Software(OSS).As in OSS many developers are involved and make changes to the code through WWW, it is prone to more defects and the changes keep on occurring. Therefore three nested techniques or three concentric loops are used to automate modelbased testing of evolving GUIbased OSS. Crash testing is the innermost technique operates on each code checkin of the GUI software and it is executed frequently with an automated GUI testing intervention and performs quickly also. It reports the software crashes back to the developer who checked in the code. Smoke testing is the second technique operates on each day39。s graphics capabilities to make the program easier to use. Graphical User Interface (GUI) provides user an immense way to interact with the software [1]. The most eminent and essential parts of the software that is being used today are Graphical User Interfaces (GUIs) [8], [9]. Even though GUIs provides user an easy way to use the software, they make the development process of the software tangled [2]. Graphical user interface (GUI) testing is the process of testing software39。International Journal of Software Engineering amp。 Applications (IJSEA), , , January 2021 STUDY PAPER ON TEST CASE GENERATION FOR GUI BASED TESTING Isabella1and Emi Retna2 1 PG Research Scholar, Software Engineering Group, School of Computer Science and Technology, Karunya University, Coimbatore, India 2 Head – Computer Technology Centre, Karunya University, Coimbatore, India ABSTRACT With the advent of WWW and outburst in technology and software development, testing the software became a major concern. Due to the importance of the testing phase in a software development lifecycle, testing has been divided into graphical user interface (GUI) based testing, logical testing, integration testing, Te