Change Detection System for the Maintenance of Automated Testing
Maintenance of automated test scripts is one of the important factors leading to success and return of investment of the test automation projects. As the key prerequisite to maintain the scripts correctly, we need to be informed about all relevant changes in the project scope, specification or system under test to be able to reflect them in updates of the test scripts. In this paper we introduce a concept on how to track these changes in semi-automated way with acceptable additional effort. The proposed solution is based on automated detection of changes in test management and requirement management tools, combined with optional manual inputs and automated scanning of changes in system under test user interface.
KeywordsTest Automation Automated Detection of Change Maintenance of Test Scripts Better Efficiency Traceability Change Management
Unable to display preview. Download preview PDF.
- 1.Rafi, D.M., et al.: Benefits and limitations of automated software testing: Systematic literature review and practitioner survey. In: 7th International Workshop on Automation of Software Test (AST), Zurich, Switzerland, pp. 36–42 (2012)Google Scholar
- 2.Dustin, E., Garrett, T., Gauf, B.: Implementing Automated Software Testing, pp. 24–26. Addison-Wesley, Boston (2009)Google Scholar
- 3.Xie, Q., Memon, A.M.: Using a Pilot Study to Derive a GUI Model for Automated Testing. ACM Transactions on Computational Logic 18(2) (November 2008)Google Scholar
- 4.Van der Alast, L., et al.: TMap Next: Business Driven Test Management. UTN Publishers, Nederlands (2008)Google Scholar
- 5.Koomen, T., et al.: TMap Next for result-driven testing. UTN Publishers, Nederlands (2006)Google Scholar
- 6.Haswell, J.J., Young, R.J., Schramm, K.: System, method, and article of manufacture for test maintenance in an automated scripting framework, US Patent 6 701 514 B1 (March 2, 2004)Google Scholar
- 7.Ibbs, C., Wong, C., Kwak, Y.: Project Change Management System. Journal of Management in Engineering 17(3) (July 2001)Google Scholar