On the Role of Communication, Documentation and Experience during System Testing - An Interview Study

The quality of business software is more and more becoming a competitive factor. As complete testing is impossible, testers have to make decisions, e.g. to choose which parts of the software have to be tested in which way. For this purpose, testers need a lot of information, e.g. input documentation which serves as a basis for the derivation of test cases or information on the project status which serves as a basis to plan the testing process. Thus, testers rely on up-to-date and complete information in order to make sound decisions. Consequently, the quality of the testing process depends on the quality of the information sources available for the testers. This paper presents the results of an interview study conducted during the SIKOSA research project with expert testers of our industry partners in order to identify the most valuable sources of information during testing. Particularly, we investigated which documents are often used by testers as well as the role of communication and experience. Our results show that defect reports are very valuable. User manuals and problem reports are equally important, because they represent real usage of the software and serve testers as input for realistic test cases. Additionally, our results show the influence of an independent testing team on test process characteristics.

[1]  Carolyn B. Seaman,et al.  The information gathering strategies of software maintainers , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[2]  C. Robert Carlson,et al.  Developing a Testing Maturity Model for software test process evaluation and improvement , 1996, Proceedings International Test Conference 1996. Test and Design Validity.

[3]  Åsa G. Dahlstedt Guidelines Regarding Requirements Engineering Practices in order to Facilitate System Testing , 2005 .

[4]  Jean Hartley,et al.  Case study research , 2004 .

[5]  Shari Lawrence Pfleeger,et al.  Principles of survey research part 6: data analysis , 2003, SOEN.

[6]  Daniel J. Mosley,et al.  Just Enough Software Test Automation , 2002 .

[7]  J. Whitney Case Study Research , 1999 .

[8]  Martin Pol,et al.  Test process improvement: a practical step-by-step guide to structured testing , 1999 .

[9]  Barbara Paech,et al.  The Testing Process - A Decision Based Approach , 2007, International Conference on Software Engineering Advances (ICSEA 2007).

[10]  Paul J. Layzell,et al.  Expert maintainers' strategies and needs when understanding software: a case study approach , 2001, Proceedings Eighth Asia-Pacific Software Engineering Conference.

[11]  B. Paech,et al.  Criteria for Software Testing Tool Evaluation – A Task Oriented View , 2005 .

[12]  Mark Dowson,et al.  The Ariane 5 software failure , 1997, SOEN.

[13]  Carolyn B. Seaman,et al.  Qualitative Methods in Empirical Studies of Software Engineering , 1999, IEEE Trans. Software Eng..

[14]  Barbara Paech,et al.  Entscheidungen im Testprozess , 2007, Software Engineering.