透過您的圖書館登入
IP:3.145.178.157
  • 學位論文

智慧型手機功能驗證與測試自動化

Smartphone application functional verification and test automation

指導教授 : 廖秀莉
若您是本文的作者,可授權文章由華藝線上圖書館中協助推廣。

摘要


2013 年第一季智慧型手機Android 作業系統市佔率高達 75%,因Android為開放程式碼,意味手機開發產業變得更為複雜,形成了廠牌手機與白牌手機的市場瓜分。本研究選擇白牌手機做為測試目標及測試自動化程式的平台,相較品牌手機,白牌手機更有產品量產的時效急迫性及客製化需求,所以必須要有完備的重點又快速的測試計畫。本研究將Android手機功能測試依照應用程式分類及測試方式、測試目標的不同,將測試分為測試工程師手動測試與自動化測試,分別提出測試個案發展方式及測試設計個案方向,探討Android手機應用程式功能的測試方式與重點,分為兩個部分進行規畫:「軟體測試個案規畫」與「測試自動化設計」。「軟體測試個案規畫」依照Android架構以及軟體測試規範,設計Android嵌入式應用軟體的測試個案腳本,目標在提出測試個案建立時必須要注意的規範及重點,因需要確認功能的正確性與錯誤防範機制,此部分為測試工程師必須手動親測。「測試自動化設計」自動化程式開發使用Android內建的工具做為選定的開發方法及工具開發測試自動化程式。自動化測試測試目標在於期望透過測試達到應用程式功能穩定性,透過分析測試結果對效能與穩定性提升提供幫助。此部分測試工程師除開發程式與環境設定外,最重要需要分析自動化之後的結果與發生問題時對系統產生的影響。為加強功能全面性測試與系統穩定性測試,必須要測試工程師與自動化測試同步做搭配測試是較為省時又有效率的方式。測試的成效最重要的因素之一就是取決於測試的前置作業也就是測試個案與測試自動化程式的準備,將功能明確分類之後依照其特性做適當的測試方式,對智慧型手機功能做驗證對於測試效能與效率皆可提升。

並列摘要


In the first quarter of 2013, market share of Android Smartphone raised up to 75%. Because of the open source property of Android, the industry of handset development will be more and more complicated, and the market is shared by brand handsets and no-brand handsets. In this study, we choose no-brand handsets as the platform of testing targets and testing automation programs. Compared with branding handsets, there are more issues about timing urgency and customized requirements for mass production of no-brand handsets and so there must be complete points and rapid testing plans. We separate the testing to manual test by engineers and automated test according to application categories, test methods and test targets of the functionality of Android handsets. And we propose developing methods of testing cases and testing design of case directions to discover the testing methods and points of the application functionality of Android handsets. It is divided into two parts to proceed: “case planning of software testing” and “test automation design.”For “case planning of software testing” we design scripts for testing cases of Android-embedded application software according to Android architecture and software testing policies. Our goal is to find the rules and points for establishing a testing case. In this part testing engineers personally have to test manually to confirm the correctness of functionality and the error-prevention mechanism. For “test automation design” we design automation program using the tools built in Android to develop automation programs. The goal of automation test is to achieve the stableness of applications and improve the effectiveness and the stableness by the analysis results of tests. In this part the most important thing for test engineers is to analyze the results after automation and the system influence when problems occur, besides developing programs and setting up the environments. To enhance the test of full functionality and system stability, it is a much efficient way that test engineers do the tests synchronizing with automation tests. One of the most important factors of testing effectiveness is determined by the pre-operation of the test - that is the preparation of the test cases and test automation programs. It will improve the effectiveness and efficiency of tests by clearly categorizing the functionality, choosing proper test methods and verifying the functionality of handset.

參考文獻


李復孝、馬維銘、趙善中. (2009). 以架構導向改善軟體測試管理模型之研究. [Architecture-Oriented Approach to Enhance Software Testing Management Model]. 資訊管理展望, 11(1), 73-93.
沈芊俐. (2012). 行動通訊之軟體品質保證─綜觀Android手機測試. [Software Quality Assurance for Mobile Communication-A Comprehensive Prospective on Android Smart Phone Test]. 品質月刊, 48(7), 14-18.
Gilbert, Peter. (2011). Automating privacy testing of smartphone applications. Duke University.
Hetzel, Bill. (1988). The Complete Guide to Software Testing.
英文部分:

延伸閱讀