The platform will undergo maintenance on Sep 14 at about 7:45 AM EST and will be unavailable for approximately 2 hours.
2009 IEEE International Conference on Software Maintenance 2009
DOI: 10.1109/icsm.2009.5306286
|View full text |Cite
|
Sign up to set email alerts
|

Guide: A GUI differentiator

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
10
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 16 publications
(10 citation statements)
references
References 2 publications
0
10
0
Order By: Relevance
“…During this modification, developers may introduce a fault in the code that results in a presentation failure. Existing techniques, such as Cross-Browser Testing (XBT) [19], [7], [8], GUI differencing [26], automated oracle comparators [21], or tools based on diff may be of limited use in this scenario. The reason for this is that these techniques use a tree-based representation (e.g., DOM) to compare the versions of the faulty web page.…”
Section: Motivating Scenariosmentioning
confidence: 99%
See 1 more Smart Citation
“…During this modification, developers may introduce a fault in the code that results in a presentation failure. Existing techniques, such as Cross-Browser Testing (XBT) [19], [7], [8], GUI differencing [26], automated oracle comparators [21], or tools based on diff may be of limited use in this scenario. The reason for this is that these techniques use a tree-based representation (e.g., DOM) to compare the versions of the faulty web page.…”
Section: Motivating Scenariosmentioning
confidence: 99%
“…For example, many techniques are focused on one type of presentation failure, such as CrossBrowser Issues (XBIs) (e.g., [19], [7], [8]), or a limited and predefined set of application-independent failure types (e.g., Fighting Layout Bugs [23]), and cannot detect other types of presentation failures. Other techniques can only support debugging efforts where there is a prior working version that can be compared against (e.g., [26], [21]). Finally, a group of techniques require testers to exhaustively specify all correctness properties to be checked (e.g., Selenium [4], CrawlJax [16], Cucumber [1], and Sikuli [6]), which is laborintensive and potentially error-prone.…”
Section: Introductionmentioning
confidence: 99%
“…Examples of these techniques include Cross Browser Testing (XBT) [11,6], GUI differencing [25], and automated oracle comparators [21]. These techniques compare tree based representations (e.g., GUI tree or HTML DOM) of the current user interface against a reference version, and use differences between these representations to find failures and faults.…”
Section: Limitations Of Existing Techniquesmentioning
confidence: 99%
“…These tools are capable of only verifying the syntactical correctness, and not the actual visual appearance of the web page. Another group of techniques, such as cross-browser testing [11] and GUI differencing [25], can also find presentation failures. However, these approaches assume the existence of a bug-free previous version of the web application and detect failures by comparing against this version.…”
Section: Introductionmentioning
confidence: 99%
“…GUI Differencing: The most closely related work to ours is that by Xie et al who introduced a GUI differencing approach called Guide [50]. Guide is capable of resolving mappings between GUI objects of GUI hierarchy trees in different app versions, however, its matching procedure is not described in detail.…”
Section: Related Workmentioning
confidence: 99%