摘要(英) |
System integration plays an important role in a software development process. Moreover, environment factors such as the development processes, programming languages, OS platforms, and the ways of compiling or installing applications make the continue integration systems for traditional PC-based applications may not be applicable for developing Android-based applications.
Without the supporting of such tools or systems, the team member(s) of an Android-based application project will have to build entire applications manually. In a large project, such procedure will be more difficult to be realized and waste many human resources. Even more, it will also cause the deployment process to be inefficient, comprise the software quality, or make the entire project fail.
In order to support the development and integration of Android-based applications, we enhanced our previously developed Daily Build and Auto Test (DBAT) system to be a continuous integration tool for dealing with some kinds of repeat works in building Android applications, including automatically compiling, testing and deployment.
|
參考文獻 |
[1] Steve Mcconnell, "Daily Build and Smoke Test," IEEE Software, vol. 13, no. 4, pp. 144,143, July 1996
[2] Richard Hsu, 基於服務導向架構之每日建置與自動測試系統設計與實作, July 2008
[3] Jhe-yu Liou, 改良每日建置與自動測試系統於開發服務導向架構系統, July 2009
[4] Fowler, Martin. "Continuous Integration", From http://www.martinfowler.com/articles/continuousIntegration.html.
[5] Troy Magennis, ”Continuous Integration and Automated Builds at Enterprise Scale”, November 2007
[6] Ron Jeffries, Ann Anderson, Chet Hendrickson, “Extreme Programming Installed”, 2001
[7] “The Rules of Extreme Programming”, From http://www.extremeprogramming.org/rules/integrateoften.html
[8] G. Myers. The Art of Software Testing. John Wiley and Sons, New York NY, 1979.
[9] Wikipedia, “Test-driven development”, 24 June 2010 , From http://en.wikipedia.org/wiki/Test-driven_development
[10] Jeff Patton, “Test-Driven Development Isn’t Testing”, From http://www.stickyminds.com/sitewide.asp?ObjectId=8497&Function=DETAILBROWSE&ObjectType=COL
[11] Wikipedia, “Code coverage”, 3 July 2010, From http://en.wikipedia.org/wiki/Code_coverage
[12] Steve Cornett, “Code Coverage Analysis”, From http://www.bullseye.com/coverage.html
[13] “What is Android?” , 2 Jul 2010, From http://developer.android.com/guide/basics/what-is-android.html
[14] “Application Fundamentals”, 2 Jul 2010, From http://developer.android.com/guide/topics/fundamentals.html
[15] Wikipedia, “Dalvik (software)”, 5 July 201, From http://en.wikipedia.org/wiki/Dalvik_(software)
[16] “Apache Gump”, From http://gump.apache.org/
[17] “Automated Build Studio”, From http://www.automatedqa.com/products/abs
[18] “How to get EMMA code coverage of Android”, From http://duykham.blogspot.com/2009/09/how-to-get-emma-code-coverage-of.html
[19] Android Developers Group, “ EMMA Code coverage and JUnit ”, From http://groups.google.com/group/android-developers/browse_thread/thread/43cf8a8ca5662f85?tvc=2
[20] “Bamboo”, From http://www.atlassian.com/software/bamboo/
[21] “BuildBot”, From http://en.wikipedia.org/wiki/BuildBot
[22] “Ant”, From http://ant.apache.org/
[23] “EMMA”, From http://emma.sourceforge.net/
|