Generalizing WYSIWYT visual testing to screen transition languages

Brown, Darren; Burnett, Margaret; Rothermel, Gregg; Fujita, Hamido; Negoro, Fumio

doi:10.1109/hcc.2003.1260230

Cited by 6 publications

(2 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It includes support for reasoning about regions of cells with shared formulas [Fisher et al 2006b;Burnett et al 2002] and also interacts with assertions (covered in Section 3.2), fault localization, debugging (covered in Section 3.5), reuse of prior test cases [Fisher et al 2002b], and the "Help Me Test" functionality mentioned earlier. There has also been research into how WYSIWYT can be applied to visual dataflow languages [Karam and Smedley 2002] and to the kind of "screen transition" programming being developed for web page design [Brown et al 2003]. …”

Section: Detecting Errors With Testingmentioning

confidence: 99%

The state of the art in end-user software engineering

Abraham

Beckwith³

et al. 2011

ACM Comput. Surv.

485

268

View full text Add to dashboard Cite

Most programs today are written not by professional software developers, but by people with expertise in other domains working towards goals for which they need computational support. For example, a teacher might write a grading spreadsheet to save time grading, or an interaction designer might use an interface builder to test some user interface design ideas. Although these end-user programmers may not have the same goals as professional developers, they do face many of the same software engineering challenges, including understanding their requirements, as well as making decisions about design, reuse, integration, testing, and debugging. This article summarizes and classifies research on these activities, defining the area of End-User Software Engineering (EUSE) and related terminology. The article then discusses empirical research about end-user software engineering activities and the technologies designed to support them. The article also addresses several crosscutting issues in the design of EUSE tools, including the roles of risk, reward, and domain complexity, and self-efficacy in the design of EUSE tools and the potential of educating users about software engineering principles.

show abstract

Section: Detecting Errors With Testingmentioning

confidence: 99%

The state of the art in end-user software engineering

Abraham

Beckwith³

et al. 2011

ACM Comput. Surv.

485

268

View full text Add to dashboard Cite

show abstract

“…The information bases of our approaches are coupled with the WYSIWYT testing methodology, which has been shown to be generalizable to other spreadsheet systems such as Excel [27], and to other programming paradigms such as the dataflow paradigm using Prograph [32], and to the screen transition paradigm using Lyee [10]. Our mappings can be adapted as needed to map these information bases into suitable fault localization feedback in the given programming paradigm.…”

Section: Conclusion and Implications For Future Workmentioning

confidence: 99%

Interactive fault localization techniques in a spreadsheet environment

Ruthruff

Burnett

Rothermel

2006

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

End-user programmers develop more software than any other group of programmers, using software authoring devices such as multimedia simulation builders, e-mail filtering editors, by-demonstration macro builders, and spreadsheet environments. Despite this, there has been only a little research on finding ways to help these programmers with the dependability of the software they create. We have been working to address this problem in several ways, one of which includes supporting end-user debugging activities through interactive fault localization techniques. This article investigates fault localization techniques in the spreadsheet domain, the most common type of end-user programming environment. We investigate a technique previously described in the research literature, and two new techniques. We present the results of an empirical study to examine the impact of two individual factors on the effectiveness of fault localization techniques. Our results reveal several insights into the contributions such techniques can make to the end-user debugging process, and highlight key issues of interest to researchers and practitioners who may design and evaluate future fault localization techniques.

show abstract