【文章內(nèi)容簡介】 ext 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 GUI build and performs functional reference testing of the newly integrated version of the GUI, using the previously tested version as a baseline. Comprehensive Testing is the outermost third technique conducts detailed prehensive GUI integration testing of a major GUI release and it is executed after a major version of GUI is available. Problems are reported to all the developers who are part of the development of the particular version. These concentric loops provide resource utilization, errors are caught earlier by inner loops. The flaws that persist across multiple versions GUIbased OSS are detected by this approach fully automatically. It provides feedback. The limitation is that the interactions between the three loops are not defined. . Continuously Evolving GUIBased Software Applications Qing Xie and Atif M. Memon [9], developed a quality assurance mechanism to manage the quality of continuously evolving software by Presenting a new type of GUI testing, called crash testing to help rapidly test the GUI as it evolves. Two levels of crash testing is being described: immediate feedbackbased crash testing in which a developer indicates that a GUI bug was fixed in response to a previously reported crash。 only the select crash test cases are re run and the developer is notified of the results in a matter of seconds. If any code changes occur, new crash test cases are generated and executed on the GUI. Test cases are generated that can be generated and executed quickly and cover all GUI functionalities. Once EIG is obtained, a boolean flag is associated with each edge in the graph. During crash testing, once test cases that cover that particular edge are generated, then the flag is set. If any changes occur, boolean flag for each edge is retained. Test cases are executed and crashes during test execution are used to identify serious problems in the software. The crash testing process is shown in Figure 4. The effectiveness of crash test is known by the total number of test cases used to detect maximum faults. Significantly, test suite size has no impact on number of bugs revealed. This crash testing technique is used to maintain the quality of the GUI application and it also helps in rapidly testing the application. The drawbacks are, this technique is used for only testing GUI application and cannot used in web applications, Fault injection or seeding technique, which is used to evaluate the efficiency of the method used is not applied here. Figure 4. Crash Testing Process . Rapidly Evolving Software Atif M. Memon et al [10], made several contributions in the area of GUI smoke testing in terms of GUI smoke test suites, their size, fault detection ability and test oracle. Daily Automated Regression Tester (DART) framework is used to automate GUI smoke testing. Developers work on the code during day time and DART automatically launches the Application Under Test (AUT) during night time, builds it and runs GUI smoke tests. Coverage and error report are mailed to developer. In DART all the process such as Analyzing the AUT’s GUI structure using GUI ripper, Test case generation, Test oracle generation, Test case executor, Examining the reports and unsuccessful test cases, Submitting bug reports are automated. GUI smoke test cases and test oracles are generated. Fault seeding is used to evaluate fault detection techniques used. An adequate number of faults of each fault type are seeded fairly. The disadvantages are Some part of code are missed by smoke tests, Some of the bugs reported by DART are false positive, Overall effectiveness of DART depends on GUI ripper capabilities, Not available for industry based application testing, Faults that are not manifested on the GUI will go undetected 5. INCORPORATING EVENT CONTEXT Xun Yuan et al [1], developed a new criterion for GUI testing. They used a binatorial interaction testing technique. The main motivation of using binatorial interaction is to incorporate context and it also considers event binations, sequence length and include all possible event. Graph models are used and covering array is used to generate test cases which are the basis for binatorial interaction testing. A tool called GUITAR (GUI Testing Framework) is used for testing and this provides functionalities like generate test cases, execute test cases, verify correctness and obtain coverage reports. Initially using GUI ripper, a GUI application is converted into event graph and then the events are grouped depending on functionality and constraints are identified. Covering array is generated and test sequences are produced. Test cases are generated and executed. Finally coverage is puted and a test adequacy criterion is analyzed. The advantages are: contexts are incorporated, detects more faults when pared to the previous techniques used. The disadvantages are infeasible test cases