12,000

We have over 12,000 students, from over 100 countries, within one of the safest campuses in the UK

93%

93% of Lancaster students go into work or further study within six months of graduating

Home > Research > Publications & Outputs > 'Good' Organisational Reasons for 'Bad' Softwar...
View graph of relations

« Back

'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company

Research output: Contribution in Book/Report/ProceedingsPaper

Published

Publication date1/05/2007
Host publicationSoftware Engineering, 2007. ICSE 2007. 29th International Conference on
PublisherIEEE
Pages602-611
Number of pages10
ISBN (Print)0-7695-2828-7
Original languageEnglish

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.