• Abstract
• Full-Text PDF [345 KB]
• Full-Text XML
• Article Versions Notes

• Article Statistics
• Google Scholar
• Order Reprints

• Cite this article
• Export to BibTeX
• Export to EndNote

• [+] on DOAJ
• Mugridge, R
• Utting, M
• Streader, D
• [+] on Google Scholar
• Mugridge, R
• Utting, M
• Streader, D
• [+] on PubMed
• Mugridge, R
• Utting, M
• Streader, D

•  CiteULike
•  Facebook
•  Mendeley
•  Twitter

This article is

• freely available
• re-usable

Future Internet 2011, 3(2), 159-174; doi:10.3390/fi3020159

Article

Evolving Web-Based Test Automation into Agile Business Specifications

Rick Mugridge ^1,* , Mark Utting ¹  and David Streader ²

¹ Rimu Research, 271 Ararimu Valley Road, RD 2 Waimauku , Auckland 0882, New Zealand ² Department of Computer Science, University of Waikato, Private Bag 3105, Hamilton 3240, New Zealand

* Author to whom correspondence should be addressed.

Received: 31 March 2011; in revised form: 26 May 2011 / Accepted: 27 May 2011 / Published: 3 June 2011

(This article belongs to the Special Issue Agile Practices)

Download PDF Full-Text [345 KB, uploaded 3 June 2011 12:42 CEST]

Abstract: Usually, test automation scripts for a web application directly mirror the actions that the tester carries out in the browser, but they tend to be verbose and repetitive, making them expensive to maintain and ineffective in an agile setting. Our research has focussed on providing tool-support for business-level, example-based specifications that are mapped to the browser level for automatic verification. We provide refactoring support for the evolution of existing browser-level tests into business-level specifications. As resulting business rule tables may be incomplete, redundant or contradictory, our tool provides feedback on coverage.

Keywords: web test automation; agile; business specifications; abstraction; coverage

Article Statistics

Cite This Article