This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
29th International Conference on Software Engineering (ICSE'07)
'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company
Minneapolis, Minnesota
May 20-May 26
ISBN: 0-7695-2828-7
ASCII Text
x 
 
David Martin, John Rooksby, Mark Rouncefield, Ian Sommerville, "'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company," Software Engineering, International Conference on, pp. 602-611, 29th International Conference on Software Engineering (ICSE'07), 2007.
 
 
BibTex
x
 
@article{ 10.1109/ICSE.2007.1,
author = {David Martin and John Rooksby and Mark Rouncefield and Ian Sommerville},
title = {'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company},
journal ={Software Engineering, International Conference on},
volume = {0},
year = {2007},
issn = {0270-5257},
pages = {602-611},
doi = {http://doi.ieeecomputersociety.org/10.1109/ICSE.2007.1},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Software Engineering, International Conference on
TI - 'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company
SN - 0270-5257
SP602
EP611
A1 - David Martin,
A1 - John Rooksby,
A1 - Mark Rouncefield,
A1 - Ian Sommerville,
PY - 2007
KW - null
VL - 0
JA - Software Engineering, International Conference on
ER -
 
David Martin, XRCE, Grenoble
John Rooksby, Lancaster University, UK
Mark Rouncefield, Lancaster University, UK
Ian Sommerville, University of St Andrews, UK
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.
Citation:
David Martin, John Rooksby, Mark Rouncefield, Ian Sommerville, "'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company," icse, pp.602-611, 29th International Conference on Software Engineering (ICSE'07), 2007
Usage of this product signifies your acceptance of the Terms of Use.