Step by Step process for Robotium With APK file for Android

Robotium with APK.

Step 1 :            Start Eclipse

Step 2:             File →  New →  other → Android → Android Test Project → Project name → Next → This project → Next → Android version → finish

Step 3:             To find Launcher activity ID and launcher activity Name
                        Open the Respective application from emulator.

Step 4 :            kalyan@kumar-desktop:~/android-sdk-linux/platform-tools$ ./adb logcat

Step 5:             Find the last line (I/ActivityManager(   59): Displayed activity com.ni.sniffer/.Sniffer: 922 ms (total 922 ms))

Step 6:             Here Target Package is “com.ni.sniffer”

Step 7:             Launcher activity is “com.ni.sniffer.Sniffer” (Case sensitive)

Step 8:             Open the AndroidManifest.xml from res folder

Step 9:             Change the target package and save then close

Step 10:           Right click package, New → class

Step 11:           Change package and give name

Step 12:           Coding with similar changes

Step 13:           Right click on project Build path → Configure build path → libraries → Add external JARs and browse the Robotium.jar

Step 14:           Select order and export tab and select the Robotium and then click OK.

Step 15:           Signature

Step 15.1:        Unzip the apk zip file

Step 15.2:        Delete the Meta-INF file

Step 15.3:        Rezip the file

Step 15.4:        Open the Terminal

Step 15.5:        kalyan@kumar-desktop:~/android-sdk-linux/platform-tools$  jarsigner -keystore ~/.android/debug.keystore -storepass android -keypass android '/home/kalyan/Desktop/Working/APKs_to_work/Sniffer/Sniffer.apk.zip'                             

 androiddebugkey

Step 15.6:  kalyan@kumar-desktop:~/android-sdk-linux/tools$ zipalign '/home/kalyan/Desktop/Working/APKs_to_work/Sniffer/Sniffer.apk.zip' Sniffer1.apk
Note : Sniffer1.apk is the new name which given by us.

Step 16:           Right click the project Run as →Android Junit Test                                          

Comments

Post a Comment

Popular posts from this blog

Online Tricentis Tosca Automation Training with Real Time Scenarios

ONLINE TRICENTIS TOSCA AUTOMATION TRAINING WITH REAL TIME SCENARIOS TOSCA COURSE CONTENT (40 Hours) Tosca has become an leading Automation tool in market migrating most of the existing projects to tosca, which has an excellent flexibility to handle script-free automation tool. This training helps the team to write complex/simple automation scripts very easily and can able to handle any type of scenarios. Here with providing the list of topics covered under this course: Tosca Introduction  (Duration 2 Hours) Brief about Tricentis Tosca Testsuite Overview and concept Business dynamic TestCases and test automation System Requirements for Tricentis Tosca Testsuite Installing Tosca Installation process Unattended installation  License administration Node Locked License Floating License Commuter License Cloud License Specific License Files and directories Maintaining the Tosca installation (Duration 2 Hours) Working Features in TOSCA The Men...
Continue Reading »

Online Selenium Training With Real Time Scenario

SELENIUM TRAINING COURSE CONTENT Introduction ü What is automation testing ü When to go for automation ü Different automation tools (vendor & open source tools) ü Advantages of  automation ü Difference between manual testing & Automation testing process                                     Introduction to selenium ü What is selenium Tool ü Use of selenium tool in automation ü Features of selenium tool ü Differences  between selenium and other tools Selenium Components ü Selenium IDE ü Selenium RC ü Selenium WebDriver ü Selenium  Grid Configuration of selenium IDE & Dev. Scripts ü Installing/Downloading Selenium IDE ü Features of Selenium IDE ü Recording/Creating your first test with Selenium IDE ü Script Debugging in Selenium IDE. ...
Continue Reading »

How to move application from development server to production server

Hi friends today I am talking about how to move code from development to a production server this is nothing but release management life cycle but it is an important aspect for tester. The Release management discipline covers moving code form a developer’s machine to production.  This will be done in this way: Developer develops code and runs unit test, integration tests review the code prior to putting it in to the main build, which then leads to Install and build test server, this is where the install team install the code which has come out of the build, if the build does not work then the release manager knows there is a problem, most companies have a code curfew where they make sure developers don’t submit code for the nights build unless they have tested it. If the install is ok a regression test is run and if this passes, then the code is release to the test team, on one or more ideally two test servers. The testers then run their test scripts against the test plan and tes...
Continue Reading »