'Good' organisational reasons for 'bad' software testing: An ethnographic study of testing in a small software company

David Martin, John Rooksby, Mark Rouncefield, Ian Sommerville

Research output: Chapter in Book/Report/Conference proceedingConference contribution

68 Citations (Scopus)

Abstract

In this paper we report on an ethnographic study of a small software house to discuss the practical work of software testing. Through use of two rich descriptions, we discuss that 'rigour' in systems integration testing necessarily has to be organisationally defined Getting requirements 'right', defining 'good' test scenarios and ensuring 'proper' test coverage are activities that need to be pragmatically achieved taking account of organisational realities and constraints such as: the dynamics of customer relationships; using limited effort in an effective way; timing software releases; and creating a market. We discuss how these organisational realities shape (1) requirements testing; (2) test coverage; (3) test automation; and (4) test scenario design.

Original languageEnglish
Title of host publication ICSE 2007: 29th International Conference on Software Engineering, Proceedings
PublisherIEEE Computer Society
Pages602-611
Number of pages10
ISBN (Print)978-0-7695-2828-1
DOIs
Publication statusPublished - 2007
Event29th International Conference on Software Engineering (ICSE 2007) - Minneapolis, Minnesota, United States
Duration: 20 May 200726 May 2007

Publication series

NameInternational Conference on Software Engineering
ISSN (Print)0270-5257

Conference

Conference29th International Conference on Software Engineering (ICSE 2007)
Country/TerritoryUnited States
CityMinneapolis, Minnesota
Period20/05/0726/05/07

Fingerprint

Dive into the research topics of ''Good' organisational reasons for 'bad' software testing: An ethnographic study of testing in a small software company'. Together they form a unique fingerprint.

Cite this