A Method of Minimum Reusability Estimation for Automated Software Testing

Expand
  • (1. School of Medical Information Technology, Anhui University of Traditional Chinese Medicine, Hefei 230038, China; 2. School of Management, Hefei University of Technology, Hefei 230009, China)

Online published: 2013-08-12

Abstract

Through reusing software test components, automated software testing generally costs less than manual software testing. There has been much research on how to develop the reusable test components, but few fall on how to estimate the reusability of test components for automated testing. The purpose of this paper is to present a method of minimum reusability estimation for automated testing based on the return on investment (ROI) model. Minimum reusability is a benchmark for the whole automated testing process. If the reusability in one test execution is less than the minimum reusability, some new strategies must be adopted in the next test execution to increase the reusability. Only by this way, we can reduce unnecessary costs and finally get a return on the investment of automated testing.

Cite this article

KAN Hong-xing1 (阚红星), WANG Guo-qiang1* (王国强),WANG Zong-dian1 (王宗殿), DING Shuai2 (丁 帅) . A Method of Minimum Reusability Estimation for Automated Software Testing[J]. Journal of Shanghai Jiaotong University(Science), 2013 , 18(3) : 360 -365 . DOI: 10.1007/s12204-013-1406-1

References

[1] Eickelmann N S, Richardson D J. An evaluation of software test environment architectures [C]//Proceedings of 18th International Conference on Software Engineering. Berlin, Germany: IEEE Computer Society Press, 1996: 353-364.
[2] Beizer B. Software testing techniques [M]. London: Van Nostrand Reinhold (International) Co. Ltd., 1990: 1-26.
[3] de Oliveira J C, Gouveia C C, Filho R Q. Test automation viability analysis method [EB/OL]. (2008-08-10). http://www.cesar.org.br/pdf/TestAutomationViabilityAnalysisMethod.pdf.
[4] Liu L, Zhou X S, Gu J H, et al. Agent-based automated compatibility software test for NLSF [C]//Proceedings of the Second International Conference on Machine Learning and Cybernetics. Xi’an, Shaanxi, China: IEEE Press, 2003: 1986-1989.
[5] Brooks F P. Essence and accidents of software engineering [J]. Computer, 1987, 20(4): 10-19.
[6] Hoffman D. Cost benefits analysis of test automation [C]//Software Testing Analysis & Review Conference (STARW ’99). Orlando, FL: Software Quality Methods, LLC, 1999.
[7] Kelly M. The ROI of test automation [EB/OL]. (2005-06-24). http://www.stickyminds.com/getfile. asp?ot=XML&id=8502&fn=XDD8502filelistfilename1.pdf.
[8] Lonngren D D. Reducing the cost of test through reuse [C]// IEEE Systems Readiness Technology Conference (AUTOTESTCON’98). Salt Lake City, UT, USA: IEEE Press, 1998: 48-53.
[9] Rankin C. The software testing automation framework [J]. IBM System Journal, 2002, 41(1): 126-139.
[10] Cashar E E. Development of a TPS reuse library using COTS tools [J]. IEEE Aerospace and Electronic Systems Magazine, 1997, 12(10): 12-16.
[11] Sundmark D, Pettersson A, Thane H. Regression testing of multi-tasking real-time systems: A problem statement [J]. ACM SIGBED Review, 2005, 2(2): 31-34.
[12] Skoglund M, Runeson P. A case study on regression test suite maintenance in system evolution [C]//Proceedings of 20th IEEE International Conference on Software Maintenance (ICSM ’04). Los Alamitos, CA, USA: IEEE Computer Society Press, 2004: 438-442.
[13] Fewster M, Graham D. Software test automation [M]. New York, USA: Addison-Wesley, 1999: 9-18.
[14] Boehm B W. Software engineering economics [J]. IEEE Transactions on Software Engineering, 1984, SE-10(1): 4-21.
Options
Outlines

/