Hardware Reference
In-Depth Information
Referring to Kaner's [18] question "what is a good Test case?" and his assertion that
"good TC is one that gives the required information", we see benefits in formalizing a
unified, well defined and structured TC entity that satisfies all the above dimensions.
We suggest pursuing, determining and proposing an improved and comprehensive defi-
nition of a test Case.
References
[1]
Tassey, G.: The Economic Impacts of Inadequate Infrastructure for Software Testing. Na-
tional Institute of Standards and Technology (2002)
[2]
Basili, V., Caldiera, G., McGarry, F., Pajerski, R., Page, G., Waligora, S.: The software
engineering laboratory: an operational software experience factory. In: Proceedings of the
14th international conference on Software engineering. ACM, New York (1992)
[3]
Geras, A.M., Smith, M.R., Miller, J.: A survey of software testing practices in alberta.
Canadian Journal of Electrical and Computer Engineering 29(3), 183-191 (2004)
[4]
Grindal, M., Offutt, J., Mellin, J.: On the Testing Maturity of Software Producing Or-
ganizations. In: Proceedings of the Testing: Academic and Industrial Conference-Practice
and Research Techniques TAIC PART (2006)
[5]
Ng, S.P., Murnane, T., Reed, K., Grant, D., Chen, T.Y.: A Preliminary Survey on Soft-
ware Testing Practices in Australia. In: Software Engineering Conference (2004)
[6]
Illes, T., Herrmann, A., Paech, B., Rockert, J.: Criteria for Software Testing Tool Evalua-
tion. A Task Oriented View. In: Proceedings of the 3rd World Congress for Software
Quality (2005)
[7]
Almog, D.: Verification Points for Better Testing Efficiency. In: StarEastSQE (2007)
[8]
Bach, J.: Exploratory Testing Explained,
http://www.satisfice.com/articles/et-article.pdf
[9]
Kaner, C.: The Ongoing Revolution in Software Testing. In: Software Test & Perform-
ance Conference (2004)
[10]
Gelperin, D., Hetzel, B.: The Growth of Software Testing. Communications of the
ACM 31(6), 687-695 (1988)
[11]
Ostrand, T.J., Balcer, M.J.: The Category-Partition Method for Specifying and Generat-
ing Functional Tests. Commun. ACM 31(6), 676-686 (1988)
[12]
Weyuker, E.J.: The Cost of Data Flow Testing: An Empirical Study. IEEE Transactions
on Software Engineering 16(2), 121-128 (1990)
[13]
Harrold, M.J., Rajiv, G., Mary Lou, S.: A Methodology for Controlling the Size of a Test
Suite. ACM Trans. Softw. Eng. Methodol. 2(3), 270-285 (1993)
[14]
Rosenberg, L., Hammer, T.F., Huffman, L.L.: Requirements, Testing and Metrics. In:
15th Annual Pacific Northwest Software Quality Conference (1998)
[15]
Iberle, K.: Divide and Conquer: Making Sense of Test Planning. In: The International
Conference on Software Testing, Analysis and Review, STARWEST (1999)
[16]
Aichernig, B.K.: Test-Case Calculation through Abstraction. In: International Symposium
of Formal Methods. Springer, Heidelberg (2001)
[17]
Jorgensen, P.: Software Testing: A Craftsman's Approach. CRC Press, Boca Raton
(2002)
[18]
Kaner, C.: What Is a Good Test Case? In: Star East (2003)
[19]
Grindal, M., Offutt, J., Andler, S.F.: Combination Testing Strategies: a Survey. Software
Testing Verification and Reliability 15(3), 167 (2005)
