loading...
Test-Driven Porting
Denver, Colorado July 24-July 29
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ADC.2005.46Agile Development Conference (ADC'05)
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Ralph Bohnet, ClearStream Consulting, Calgary, AB
Gerard Meszaros, ClearStream Consulting, Calgary, AB
Traditional Test-Driven Development focuses on development of new units (classes) driven by programmer-facing unit tests. This paper describes our experiences when using business-facing tests (also known as "story tests") to guide the porting of a legacy application. Domain experts specified tests in a tabular format using Excel spreadsheets. Developers automated these spreadsheets in various ways over time: scripts, generation of JUnit source code, and Fit. These tests were run against the legacy system and guided the development of the newly ported system. We found test-driven porting to be an effective way to port a complex application.
Index Terms:
Porting legacy applications,Test-Driven porting
Citation:
Ralph Bohnet, Gerard Meszaros, "Test-Driven Porting," adc, pp.259-266, Agile Development Conference (ADC'05), 2005
Usage of this product signifies your acceptance of the Terms of Use.