Automatically repairing event sequence-based GUI test suites for regression testing

Memon, Atif M.

doi:10.1145/1416563.1416564

Cited by 118 publications

(84 citation statements)

References 42 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Memon et al, [26] GUIs plays a major role of the software that is being developed and created by using rapid prototype where there is no reason for the effectiveness of the regression testing in GUI which is different from traditional software. Whenever the GUI changes or modified test cases of the original GUI is either unusable or reusable on the modified GUI.…”

Section: Module Design Phasementioning

confidence: 99%

GUI Test Script Repair in Regression Testing

Priya¹,

Rao²

2018

IJERMT

View full text Add to dashboard Cite

Abstract-UI testing is a process of testing a software application or functionality of GUI. It is defined as an interface between user and software which provides an easy way to interact with the system. GUI plays an important role in software engineering. GUI-based application requires that a test case consists of sequences of user actions/events to be executed. Selenium is an open-source tool for testing GUI Application by executing test cases whether the GUI Application is working properly or not. In this, we present test script repair technique to repair test cases. Test script repair technique uses reverse engineering process for creating the test script. Test script repair consists of three stages; they are Ripping, Mapping and Repairing. In ripping stage, there are two relationships for representing event interaction of GUI Application. During ripping we know the location of each widget. In mapping stage,original GUI events are mapped to an event-flow graph (EFG). In repairing stage, Event flow graph uses repairing transformations and human input to modified script to repair the test cases, and synthesizes a new "repaired" test script. During this process, test script repair uses GUI objects for yielding a final test script that can be executed using selenium tool to validate the GUI Application. An experiment using selenium tool to test, test cases suggests that it is effective in that unusable test scripts are repaired. Annotations significantly reduced the human cost to repair test cases.

show abstract

Section: Module Design Phasementioning

confidence: 99%

GUI Test Script Repair in Regression Testing

Priya¹,

Rao²

2018

IJERMT

View full text Add to dashboard Cite

show abstract

“…As ReAssert cannot repair broken tests when they have complex control flows or operations on expected values, Daniel et al [6,7] presented a novel test-repair technique based on symbolic execution to improve ReAssert to repair more test failures and provide better repairs. These techniques aim to repair broken unit tests in general, while some techniques have been proposed to repair broken tests in graphical user interfaces [36] or web applications [24].…”

Section: Test Repairmentioning

confidence: 99%

“…As these existing tests are developed for the old version of the software, when some of them cause failures of the new version in regression testing, the failures may not be due to bugs introduced in the modifications [36,8]. That is to say, some failures are due to bugs in the modified source code under test, but other failures are due to the obsoleteness 3 of some tests.…”

Section: Introductionmentioning

confidence: 99%

Is This a Bug or an Obsolete Test?

Hao

Lan

Zhang

et al. 2013

ECOOP 2013 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. In software evolution, developers typically need to identify whether the failure of a test is due to a bug in the source code under test or the obsoleteness of the test code when they execute a test suite. Only after finding the cause of a failure can developers determine whether to fix the bug or repair the obsolete test. Researchers have proposed several techniques to automate test repair. However, test-repair techniques typically assume that test failures are always due to obsolete tests. Thus, such techniques may not be applicable in real world software evolution when developers do not know whether the failure is due to a bug or an obsolete test. To know whether the cause of a test failure lies in the source code under test or in the test code, we view this problem as a classification problem and propose an automatic approach based on machine learning. Specifically, we target Java software using the JUnit testing framework and collect a set of features that may be related to failures of tests. Using this set of features, we adopt the Best-first Decision Tree Learning algorithm to train a classifier with some existing regression test failures as training instances. Then, we use the classifier to classify future failed tests. Furthermore, we evaluated our approach using two Java programs in three scenarios (within the same version, within different versions of a program, and between different programs), and found that our approach can effectively classify the causes of failed tests.

show abstract

“…Third, GUIs tend to change drastically over the course of development. A GUI test can show up as failing although the underlying code is actually working [19] [20]. This is especially important since a large number of false alarms from the GUI testing suite will cause developers to lose confidence in their regression suite [21].…”

Section: Test-driven Development Of Graphical User Interfacesmentioning

confidence: 99%

“…A simpler approach to UITDD involves the creation of an automated low-fidelity prototype using a program like ActiveStory Enhanced [24] or SketchFlow 20 . These prototypes are event-based GUIs that respond to user input in the same way in which actual GUIs do.…”

Section: Test-driven Development Of Graphical User Interfacesmentioning

confidence: 99%

People-Centered Software Development: An Overview of Agile Methodologies

Maurer

Hellmann

2013

Software Engineering

View full text Add to dashboard Cite

Abstract. This chapter gives an overview of agile software development processes and techniques. The first part of the chapter covers the major agile project management techniques with a focus on project planning. Iteration planning and interaction design approaches are given special focus. The second part of the chapter covers agile quality assurance with a focus on test-driven development and the state space of testing. Current problems in agile testing, including measuring test quality and testing applications with large state spaces, are discussed.

show abstract

Automatically repairing event sequence-based GUI test suites for regression testing

Cited by 118 publications

References 42 publications

GUI Test Script Repair in Regression Testing

GUI Test Script Repair in Regression Testing

Is This a Bug or an Obsolete Test?

People-Centered Software Development: An Overview of Agile Methodologies

Contact Info

Product

Resources

About