Home > Research > Publications & Outputs > 'Good' Organisational Reasons for 'Bad' Softwar...

Research

Associated organisational unit

Links

Text available via DOI:

View graph of relations

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

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company. / Martin, D.; Rooksby, J.; Rouncefield, M. et al.
Software Engineering, 2007. ICSE 2007. 29th International Conference on. IEEE, 2007. p. 602-611.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Martin, D, Rooksby, J, Rouncefield, M & Sommerville, I 2007, 'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company. in Software Engineering, 2007. ICSE 2007. 29th International Conference on. IEEE, pp. 602-611. https://doi.org/10.1109/ICSE.2007.1

APA

Martin, D., Rooksby, J., Rouncefield, M., & Sommerville, I. (2007). 'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company. In Software Engineering, 2007. ICSE 2007. 29th International Conference on (pp. 602-611). IEEE. https://doi.org/10.1109/ICSE.2007.1

Vancouver

Martin D, Rooksby J, Rouncefield M, Sommerville I. 'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company. In Software Engineering, 2007. ICSE 2007. 29th International Conference on. IEEE. 2007. p. 602-611 doi: 10.1109/ICSE.2007.1

Author

Martin, D. ; Rooksby, J. ; Rouncefield, M. et al. / 'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company. Software Engineering, 2007. ICSE 2007. 29th International Conference on. IEEE, 2007. pp. 602-611

Bibtex

@inproceedings{0e1e77a27eae4587b19466375d95f9aa,
title = "'Good' Organisational Reasons for 'Bad' Software Testing: An Ethnographic Study of Testing in a Small Software Company",
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.",
author = "D. Martin and J. Rooksby and M. Rouncefield and I. Sommerville",
year = "2007",
month = may,
day = "1",
doi = "10.1109/ICSE.2007.1",
language = "English",
isbn = "0-7695-2828-7",
pages = "602--611",
booktitle = "Software Engineering, 2007. ICSE 2007. 29th International Conference on",
publisher = "IEEE",

}

RIS

TY - GEN

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

AU - Martin, D.

AU - Rooksby, J.

AU - Rouncefield, M.

AU - Sommerville, I.

PY - 2007/5/1

Y1 - 2007/5/1

N2 - 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.

AB - 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.

U2 - 10.1109/ICSE.2007.1

DO - 10.1109/ICSE.2007.1

M3 - Conference contribution/Paper

SN - 0-7695-2828-7

SP - 602

EP - 611

BT - Software Engineering, 2007. ICSE 2007. 29th International Conference on

PB - IEEE

ER -