Utilization of extended firewall for object-oriented regression testing

White, Lee; Jaber, Khaled; Robinson, B. L.

doi:10.1109/icsm.2005.101

Cited by 19 publications

(19 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…White et al [White et al 2003] have extended their work on complete interactions sequences (CIS) to develop a new firewall [White et al 2005] regression testing approach for GUIs. A CIS is a state-machine model that partitions the GUI state space into different machines based on user tasks [White and Almezen 2000].…”

Section: Related Workmentioning

confidence: 99%

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

Memon

2008

ACM Trans. Softw. Eng. Methodol.

118

View full text Add to dashboard Cite

Although graphical user interfaces (GUIs) constitute a large part of the software being developed today and are typically created using rapid prototyping, there are no effective regression testing techniques for GUIs. The needs of GUI regression testing differ from those of traditional software. When the structure of a GUI is modified, test cases from the original GUI's suite are either reusable or unusable on the modified GUI. Because GUI test case generation is expensive, our goal is to make the unusable test cases usable, thereby helping to retain the suite's event coverage. The idea of reusing these unusable (obsolete) test cases has not been explored before. This paper shows that a large number of test cases become unusable for GUIs. It presents a new GUI regression testing technique that first automatically determines the usable and unusable test cases from a test suite after a GUI modification, then determines the unusable test cases that can be repaired so that they can execute on the modified GUI, and finally uses repairing transformations to repair the test cases. This regression testing technique along with four repairing transformations has been implemented. An empirical study for four open-source applications demonstrates that (1) this approach is effective in that many of the test cases can be repaired, and is practical in terms of its time performance, (2) certain types of test cases are more prone to becoming unusable, and (3) certain types of "dominator" events, when modified, make a large number of test cases unusable.

show abstract

Section: Related Workmentioning

confidence: 99%

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

Memon

2008

ACM Trans. Softw. Eng. Methodol.

118

View full text Add to dashboard Cite

show abstract

“…While explicit program dependencies were used for the construction of the original firewalls, hidden dependencies are included in the construction of more sophisticated firewalls and they increase the chance to intercept the residual bugs [25].…”

Section: Application In Regression Testingmentioning

confidence: 99%

Computation of Static Execute After Relation with Applications to Software Maintenance

Beszedes

Gergely

Jász

et al. 2007

2007 IEEE International Conference on Software Maintenance

View full text Add to dashboard Cite

show abstract

“…Many researchers have addressed the regression testing problem (and particularly the regression test selection problem) in the literature (Rothermel, 1993;Kung, 1995;Rothermel, 1997;Abdullah, 1998;Von Mayrhauser, 1999;Wu, 1999;Le Traon, 2000;Rothermel, 2000;Briand, 2002;Skoglund, 2005;White, 2005;Pilskalns, 2006;Engström, 2008;Engström, 2009). The selection of adequate test cases can be made in different ways.…”

Section: Introductionmentioning

confidence: 99%

Regression Testing of Object-Oriented Software: A Technique Based on Use Cases and Associated Tool

Vincent

Badri

2012

Computer Applications for Software Engineering, Disaster Recovery, and Business Continuity

View full text Add to dashboard Cite

Abstract. This paper presents a regression testing technique (and associated tool) for object-oriented software based on use cases. The basic models we use to describe use cases are UML statechart and collaboration diagrams. The technique combines, in fact, the analysis of these models to a simple static analysis of the code. The goal is to identify changes that may not be visible in design models (change in a method's body). The developed tool identifies modified (impacted by modifications) use cases and selects the appropriate test cases from an existing test suite. New test cases are generated when necessary. The selected test cases (including the new ones) are automatically executed. A case study is reported to provide evidence of the feasibility of the approach and its benefits (reduction of regression testing effort).

show abstract

Utilization of extended firewall for object-oriented regression testing

Cited by 19 publications

References 5 publications

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

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

Computation of Static Execute After Relation with Applications to Software Maintenance

Regression Testing of Object-Oriented Software: A Technique Based on Use Cases and Associated Tool

Contact Info

Product

Resources

About