請用此 Handle URI 來引用此文件:
http://tdr.lib.ntu.edu.tw/jspui/handle/123456789/63707完整後設資料紀錄
| DC 欄位 | 值 | 語言 |
|---|---|---|
| dc.contributor.advisor | 陳彥仰 | |
| dc.contributor.author | Dian-Je Tsai | en |
| dc.contributor.author | 蔡典哲 | zh_TW |
| dc.date.accessioned | 2021-06-16T17:16:54Z | - |
| dc.date.available | 2017-08-19 | |
| dc.date.copyright | 2012-08-19 | |
| dc.date.issued | 2012 | |
| dc.date.submitted | 2012-08-17 | |
| dc.identifier.citation | [1] Cutler, K.-M. This Is What Developing For Android Looks Like. From TechCrunch. 2012/5/11 (Accessed in 2012/7/13) At http://techcrunch.com/2012/05/11/this-is- what-developing-for-android-looks-like/.
[2] Cutler, K.-M. How Do Top Android Developers QA Test Their Apps? From TechCrunch. 2012/6/2 (Accessed in 2012/7/14) At http://techcrunch.com/ 2012/06/02/android-qa-testing-quality-assurance/. [3] Kumparak, G. Don't Think Android Fragmentation Is A Problem? Most Developers Disagree. From TechCrunch. 2011/4/4 (Accessed in 2012/7/16) At http:// techcrunch.com/2011/04/04/android-fragmentation/. [4] Philosophy and Goals - Android open source project. http://source.android.com/ about/philosophy.html [5] Cutler, K.-M. Android Reaches 400 Million Device Activations, Adds 1 Million Per Day. From TechCrunch. 2012/6/27 (Accessed in 2012/7/15) At http:// techcrunch.com/2012/06/27/android-reaches-400-million-devices-activations-1- million-per-day/. [6] Android Dashboard. http://developer.android.com/about/dashboards/index.html [7] Wauters, R. Charted: Android Fragmentation. From TechCrunch. 2011/10/27 (Accessed in 2012/7/21) At http://techcrunch.com/2011/10/27/charted-android- fragmentation/. [8] Android Fragmentation Visualized - The many faces of a little green robot. From OpenSignalMaps. 2012/3/1 (Accessed in 2012/7/21) At http://opensignalmaps.com/ reports/fragmentation.php. [9] Range of screens supported - Supporting Multiple Screens - Android Developers. http://developer.android.com/guide/practices/screens_support.html#range [10] Bray, T. Android Application Error Reports. From Android Developers Blog. 2010/5/21 (Accessed in 2012/7/13) At http://android-developers.blogspot.tw/ 2010/05/google-feedback-for-android.html. [11] Hickson, I. HTML5. From W3C. 2012/3/29 (Accessed in 2012/7/15) At http:// www.w3.org/TR/html5/. [12] Amazon Web Services - Regions and Endpoints. http:// docs.amazonwebservices.com/general/latest/gr/rande.html [13] Instance Types - Amazon Elatic Compute Cloud (EC2). http://aws.amazon.com/ ec2/#instance [14] DeCandia, G., Hastorun, D., Jampani, M., Kakulapati, G., Lakshman, A., Pilchin, A., Sivasubramanian, S., Vosshall, P. and Vogels, W. 2007. Dynamo: amazon's highly available key-value store. In Proceedings of the Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles Stevenson, Washington, USA, 2007. ACM. 205-220 [15] Specifying the Primary Key - Amazon DynamoDB documentation. http:// docs.amazonwebservices.com/amazondynamodb/latest/developerguide/ WorkingWithDDTables.html#WorkingWithDDTables.primary.key | |
| dc.identifier.uri | http://tdr.lib.ntu.edu.tw/jspui/handle/123456789/63707 | - |
| dc.description.abstract | 目前市面中,有許多不同的 Android 行動裝置。每個裝置可能在作業系統版本、作業系統自定環境、以及硬體規格上有不同的差異。所謂的「Android Fragmentation」(Android 分裂)即是在描述如此的狀況,而這個分裂現象造成與其他平台相比,開發者必須投入更多的心力在開發 Android apps 中。
目前,為了解決這個問題,我們必須盡可能的在越多的 Android 行動裝置中進行測試。但是測試本身是有難度的!對測試者來說,他們往往不知道如何將測試版本的應用程式安裝到自己的行動裝置中。同時,當遇到錯誤時,測試者回報的相關資訊往往不足以讓開發者解決問題。而對開發者來說,他們也需要一個平台來管理目前釋出的測試版本。 因此,我們建立了一個叫「Cramdroid」的雲端平台來解決上述問題。我們的目的是減少開發者和測試者花費在測試活動中的成本。同時也設計了一個簡單的工作項目集來驗證 Cramdroid 的可用性。 | zh_TW |
| dc.description.abstract | There are lots of different Android devices in the market. Some are different from the OS version, some are from OS customization, and some are from hardware configuration. This is so called “Android Fragmentation”. The fragmentation makes developers put more effort into developing Android apps more than other platforms.
Currently, to solve this problem, we have to test on Android devices as more as possible. But testing itself is not quite easy. Testers don’t understand how to install the testing apps into their Android devices. Also, when an issue occurred, information reported by testers is not always enough for developers. For developers, they also need a platform to manage testing builds they distributed. Hence, we build a platform named “Cramdroid” to solve these problems. We want to reduce the cost of doing testing for both developers and testers. We also designed a simple workshop to evaluate how Cramdroid works. | en |
| dc.description.provenance | Made available in DSpace on 2021-06-16T17:16:54Z (GMT). No. of bitstreams: 1 ntu-101-R99944041-1.pdf: 2205197 bytes, checksum: 929a3986df0387e0dfb7019edfaa4726 (MD5) Previous issue date: 2012 | en |
| dc.description.tableofcontents | TABLE OF CONTENTS
誌謝 i 中文摘要 ii ENGLISH ABSTRACT iii TABLE OF CONTENTS iv TABLE OF FIGURES vi TABLE OF TABLES vii Chapter 1. INTRODUCTION 1 1.1. ANDROID FRAGMENTATION 4 1.1.1. Software Face 5 1.1.2. Hardware face 10 1.2. SOLUTION 15 1.3. CONTRIBUTION 16 1.3.1. Provide an external testing workflow for developers and testers. 16 1.3.2. Improve current debugging process in the testing workflow. 16 Chapter 2. RELATED WORK 18 2.1. Google Play Store 18 2.2. TestFlight 18 2.3. HockeyApp 19 Chapter 3. SYSTEM DESIGN 21 3.1. Android Side 21 3.2. Server Side 22 Chapter 4. IMPLEMENTATION 23 4.1. Android Client 23 4.2. Android Client (Database) - Data Models 24 4.3. Android Client (Database) - Content Provider 26 4.4. Android Client (Logcat Service) 26 4.5. Android Client (Sync Service) 28 4.6. Server Side (web-app) 29 4.7. Server Side (API and backend) - Application Server 31 4.8. Server Side (API and backend) - Static Storage and Data Store 34 4.9. Server Side (API and backend) - Process APK files 36 4.10. Server Side (API and backend) - Messaging 37 Chapter 5. EXPERIMENT DESIGN 39 Chapter 6. EXPERIMENT RESULT 42 6.1. Observations 42 6.2. Charts 45 Chapter 7. LIMITATION AND FUTURE WORK 48 Chapter 8. CONCLUSION 50 Chapter 9. BIBLIOGRAPHY 51 | |
| dc.language.iso | en | |
| dc.subject | Android | zh_TW |
| dc.subject | 雲端 | zh_TW |
| dc.subject | 亞馬遜網路服務 | zh_TW |
| dc.subject | 使用者測試 | zh_TW |
| dc.subject | 測試版本發佈 | zh_TW |
| dc.subject | 偵錯資訊收集 | zh_TW |
| dc.subject | User testing | en |
| dc.subject | Android | en |
| dc.subject | Cloud based | en |
| dc.subject | Debug information collection | en |
| dc.subject | Amazon Web Services | en |
| dc.subject | Testing app distribution | en |
| dc.title | Cramdroid: Android App 雲端測試平台 | zh_TW |
| dc.title | Cramdroid: A Cloud-based Android App Beta-testing platform | en |
| dc.type | Thesis | |
| dc.date.schoolyear | 100-2 | |
| dc.description.degree | 碩士 | |
| dc.contributor.oralexamcommittee | 蘇雅韻,金仲達,黃世昆 | |
| dc.subject.keyword | Android,雲端,亞馬遜網路服務,使用者測試,測試版本發佈,偵錯資訊收集, | zh_TW |
| dc.subject.keyword | Android,Cloud based,Amazon Web Services,User testing,Testing app distribution,Debug information collection, | en |
| dc.relation.page | 52 | |
| dc.rights.note | 有償授權 | |
| dc.date.accepted | 2012-08-18 | |
| dc.contributor.author-college | 電機資訊學院 | zh_TW |
| dc.contributor.author-dept | 資訊網路與多媒體研究所 | zh_TW |
| 顯示於系所單位: | 資訊網路與多媒體研究所 | |
文件中的檔案:
| 檔案 | 大小 | 格式 | |
|---|---|---|---|
| ntu-101-1.pdf 未授權公開取用 | 2.15 MB | Adobe PDF |
系統中的文件,除了特別指名其著作權條款之外,均受到著作權保護,並且保留所有的權利。
