A Characterisation Schema for Software Testing Techniques

One of the major problems within the software testing area is how to get a suitable set of cases to test a software system. This set should assure maximum effectiveness with the least possible number of test cases. There are now numerous testing techniques available for generating test cases. However, many are never used, and just a few are used over and over again. Testers have little (if any) information about the available techniques, their usefulness and, generally, how suited they are to the project at hand upon, which to base their decision on which testing techniques to use. This paper presents the results of developing and evaluating an artefact (specifically, a characterisation schema) to assist with testing technique selection. When instantiated for a variety of techniques, the schema provides developers with a catalogue containing enough information for them to select the best suited techniques for a given project. This assures that the decisions they make are based on objective knowledge of the techniques rather than perceptions, suppositions and assumptions.

[1]  Elaine J. Weyuker,et al.  The Cost of Data Flow Testing: An Empirical Study , 1990, IEEE Trans. Software Eng..

[2]  Gregory Tassey,et al.  Prepared for what , 2007 .

[3]  Boris Beizer,et al.  Software Testing Techniques , 1983 .

[4]  Mary Jean Harrold,et al.  Testing: a roadmap , 2000, ICSE '00.

[5]  Neil A. M. Maiden,et al.  ACRE: selecting methods for requirements acquisition , 1996, Softw. Eng. J..

[6]  Walter F. Tichy,et al.  Proceedings 25th International Conference on Software Engineering , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[7]  Natalia Juristo Juzgado,et al.  Reviewing 25 Years of Testing Technique Experiments , 2004, Empirical Software Engineering.

[8]  Thomas J. Ostrand,et al.  Experiments on the effectiveness of dataflow- and control-flow-based test adequacy criteria , 1994, Proceedings of 16th International Conference on Software Engineering.

[9]  James Miller,et al.  Comparing and combining software defect detection techniques: a replicated empirical study , 1997, ESEC '97/FSE-5.

[10]  Phyllis G. Frankl,et al.  An Experimental Comparison of the Effectiveness of Branch Testing and Data Flow Testing , 1993, IEEE Trans. Software Eng..

[11]  Rodolfo Alfredo Bertone,et al.  Software engineering: Theory and practice, 2nd Edition. Shari Lawrence Pfleeger. Prentice Hall, 2001 , 2005 .

[12]  Ian Sommerville,et al.  Software engineering (5th ed.) , 1995 .

[13]  Andreas Birk,et al.  Modelling the application domains of software engineering technologies , 1997, Proceedings 12th IEEE International Conference Automated Software Engineering.

[14]  Boris Beizer,et al.  Software testing techniques (2. ed.) , 1990 .

[15]  Sira Vegas,et al.  A Process for Identifying Relevant Information for a Repository: A Case Study for Testing Techniques , 2003 .

[16]  Meliha Handzic,et al.  Managing Software Engineering Knowledge , 2010, Springer Berlin Heidelberg.

[17]  R. Prieto-Diaz,et al.  Classification of reusable modules , 1989 .

[18]  Scott Henninger,et al.  Accelerating the successful reuse of problem solving knowledge through the domain lifecycle , 1996, Proceedings of Fourth IEEE International Conference on Software Reuse.

[19]  Will Venters,et al.  Software engineering: theory and practice , 2006 .

[20]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[21]  Phyllis G. Frankl,et al.  Further empirical studies of test effectiveness , 1998, SIGSOFT '98/FSE-6.

[22]  Victor R. Basili,et al.  Support for comprehensive reuse , 1991, Softw. Eng. J..

[23]  Victor R. Basili,et al.  Defining factors, goals and criteria for reusable component evaluation , 1996, CASCON.

[24]  Ian Sommerville Software engineering, 5th Edition , 1996 .