Mobile Application automation Process

A typical continuous integration cycle consists of the following steps:

1. The Continuous Integration server constantly checks the code status from the version control server to see if the code is updated.

2. If you find that the code has the latest commit, download the latest code from the version control server.

3. After the code is completely updated, call the automated compilation script to compile the code.

4. Run all the automated tests.

5. Perform code analysis.

6. Produce executable software that can be provided to testers for testing.

Continuous integration server, such as CruiseControl or VSTS CruiseControl, Anthill, Bamboo, TeamCity, Continuum,hudson,jenkins

This share of the overall script process is divided into 3 parts, the first part of the main building apk, the second part of the main completion of the test case (including Java and Python Code test Cases), and the third part is the completion of the results show.

The current results show the design thrust is: To send the specified message, the user access to specify the way to obtain test results to display.

Attached: APK build process step: http://blog.csdn.net/jason0539/article/details/44917745

First step: Package The resource file, generate the R.java file
The "Input" resource file (which is the file in res in the project), the assets file (which is equivalent to another resource, the Android system does not optimize it as it does for files in res), Androidmanifest.xml file (the package name is read from here, because the build R.java file requires the package name), the Android base Class library (Android.jar file)
"Output" packaged resources (generally in the Android Project Bin directory can see a file called Resources.ap_), R.java files (in the Gen directory, you should be familiar with)
The "Tools" AAPT tool, its path in ${android_sdk_home}/platform-tools/aapt (if you're using a Windows system, by convention the path should be written like this:%android_sdk_home%\ Platform-tools\aapt.exe, hereinafter).

The second step: Process the Aidl file, generate the corresponding. java files (of course, there are many projects do not use the aidl, then this process can be saved)
"Input" source files, aidl files, framework.aidl files
"Output" corresponding to the. java file
Tools Aidl Tools

Step three: Compile the Java file and generate the corresponding. class file
"Input" source files (including R.java and aidl generated. java files), library files (. jar files)
"Output". class file
Tools Javac Tools

Fourth step: Convert. class files to. dex files supported by the Davik VM
"Input". class files (including Aidl. class files, R generated. class files,. class files generated by source files), library files (. jar files)
"Output". dex File
Tools Javac Tools

Fifth step: Package to generate an unsigned. apk file
"Enter" the packaged resource file, the packaged class file (. dex file), the Libs file (including the. So file, of course, many projects do not have such a file, if you do not use C + + development)
"Output" unsigned. apk file
Tools Apkbuilder Tools

Sixth step: Sign the unsigned. apk file
"Enter" unsigned. apk file
The "output" signature of the. apk file
"Tools" Jarsigner

Seventh Step: alignment of the signed. apk file (no alignment is posted to Google Market)
"Enter" after signing the. apk file
The. apk file after the "output" is aligned
Tools Zipalign Tools

Mobile Application automation Process