How (not) to help people test drive code

Authors:
Stuart Marshall;Robert Biddle;Ewan Tempero
Affiliations:
Victoria University of Wellington, Wellington, New Zealand;Victoria University of Wellington, Wellington, New Zealand;Victoria University of Wellington, Wellington, New Zealand
Venue:
AUIC '02 Proceedings of the Third Australasian conference on User interfaces - Volume 7
Year:
2002

Citing 3
Cited 2

The cognitive walkthrough method: a practitioner's guide

Usability inspection methods
Why are CASE tools not used?

Communications of the ACM
Usability Engineering

Usability Engineering

Visualising reusable software over the web

APVis '01 Proceedings of the 2001 Asia-Pacific symposium on Information visualisation - Volume 9
A Web user interface for an interactive software repository

AUIC '04 Proceedings of the fifth conference on Australasian user interface - Volume 28

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper discusses the results of usability testing on the interface of Dyno. Dyno is a tool designed to support code reuse by helping software developers understand what a specified piece of code does. The tool does this by allowing a programmer to undertake a process we call test driving. This paper looks at the deficiencies uncovered in the initial interface, and the implications this has for a tool aimed at helping software developers better understand code fragments so as to be able to reuse them.