Cleanroom: Edit-Time Error Detection with the Uniqueness Heuristic

Ko, Andrew J.; Wobbrock, Jacob O.

doi:10.1109/vlhcc.2010.11

Cited by 5 publications

(4 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, (Ko and Wobbrock 2010) recruited hundreds of web developers online in just 1 h, avoiding the logistics of scheduling a lab-based, in-person study. Remote participation, depending on the study, can also allow participants to use their own workstations, their own space, their own tools, and even work at times of their choosing, potentially making the experiment more ecologically valid by accounting for participants natural work environments.…”

Section: Recruiting Remote Participantsmentioning

confidence: 99%

A practical guide to controlled experiments of software engineering tools with human participants

2013

View full text Add to dashboard Cite

Empirical studies, often in the form of controlled experiments, have been widely adopted in software engineering research as a way to evaluate the merits of new software engineering tools. However, controlled experiments involving human participants actually using new tools are still rare, and when they are conducted, some have serious validity concerns. Recent research has also shown that many software engineering researchers view this form of tool evaluation as too risky and too difficult to conduct, as they might ultimately lead to inconclusive or negative results. In this paper, we aim both to help researchers minimize the risks of this form of tool evaluation, and to increase their quality, by offering practical methodological guidance on designing and running controlled experiments with developers. Our guidance fills gaps in the empirical literature by explaining, from a practical perspective, options in the recruitment and selection of human participants, informed consent, experimental procedures, demographic measurements, group assignment, training, the selecting and design of tasks, the measurement of common outcome variables such as success and time on task, and study debriefing. Throughout, we situate this guidance in the results of a new systematic review of the tool evaluations that were published in over 1,700 software engineering papers published from 2001 to 2011.

show abstract

Section: Recruiting Remote Participantsmentioning

confidence: 99%

A practical guide to controlled experiments of software engineering tools with human participants

2013

View full text Add to dashboard Cite

show abstract

“…Beyond syntax errors, HTML and CSS linters apply heuristics that identify common semantic errors that a validator might not catch. For instance, Ko and Wobbrock [8] describe the uniqueness heuristic, which states that an identifier, such as an HTML ID or class, that is used only once is likely unintended. Our taxonomy suggests a number of additional warning signs for semantic errors, particularly at the rule-based level.…”

Section: Implications For Designmentioning

confidence: 99%

Towards a taxonomy of errors in HTML and CSS

Park

Saxena

Jagannath

et al. 2013

Proceedings of the Ninth Annual International ACM Conference on International Computing Education Research

View full text Add to dashboard Cite

As part of a larger research agenda to explore web development as a context for learning computational literacy skills, we investigate errors people make while writing code in HTML and CSS. We report on a lab-based study in which 20 participants were video recorded as they completed coding tasks. We have applied the skills-rules-knowledge framework to segment this data by the cognitive causes of errors they made, and present a taxonomy of these errors. Our findings demonstrate how the skills-rulesframework can be used to analyze coding errors, provide insight about the origins of these errors, and suggest ways that the design of web development tools can be improved to support learning and practice with HTML and CSS.

show abstract

“…On the other hand, latent errors, which did not express in openHTML's interface, occurred often and would sometimes cascade into a series of additional errors. While some are syntax errors that can be detected through validation, others require techniques such as the uniqueness heuristic, where a class or ID used only once throughout a project may indicate an error [9]. Through the design of openHTML, we are finding new ways of bringing these latent errors to the surface.…”

Section: Latent and Active Errorsmentioning

confidence: 99%

OpenHTML

Park

Saxena

Jagannath

et al. 2013

CHI '13 Extended Abstracts on Human Factors in Computing Systems

View full text Add to dashboard Cite

We describe the initial design rationale and early findings from studies of a web editor for beginners called openHTML. We explain our strategy of transitional design that views web editors as a part of a complex socio-technical system that spans multiple tools, practices, and actors. Our goal is to create a toolkit that can engage beginners in meaningful activities now and prepare them for more sophisticated activities in the future.

show abstract

Cleanroom: Edit-Time Error Detection with the Uniqueness Heuristic

Abstract: Abstract

Cited by 5 publications

References 11 publications

A practical guide to controlled experiments of software engineering tools with human participants

A practical guide to controlled experiments of software engineering tools with human participants

Towards a taxonomy of errors in HTML and CSS

OpenHTML

Contact Info

Product

Resources

About