In my last company blog post I dealed with the topic: “How to choose the right mobile test devices”.
In addition to all our mobile test automation, we also do a lot of manual and exploratory testing within our mobile team. We test devices with different hard- and software, with different browser versions, and on different carrier networks to be sure that our apps work in the way our customers will use it.
Due to the fact that the mobile market is growing, the key question for a mobile Quality Assurance person is: Which devices are right for testing? It’s simply not possible to do testing on every device!
This week I attended the Mobile Developer Conference in Hamburg/ Germany. In the talk from Miroslav Simudvarac (www.troido.de) he presented some really useful Android Development Tools. I really like the tools and I think they are really helpful for Android Developers or Quality Assurance Experts.
The first tool is the so called re-signer developed by Miroslav Simudvarac. If you want to test e.g. with Robotium against an existing APK file and you don’t have access to the source code, you need to resign the APK file with your own signature. In a previous post I explained why you have to change the signature and how to do this on a commandline. With the re-signer tool you are now able to resign APK files over a graphical user interface. All you need ist the re-sign.jar file and an installed Android SDK. The tool can be downloaded from here. Download the jar file and execute it with a double click or from commandline with java -jar re-sign.jar. The following user interface should show up.
To resign your APK file, just Drag & Drop the file in the window. If the resigning was successful a popup window will show up and give you the information about the starting activity and the package name of the APK file that you need for your Robotium Manifest.xml file. Thats it! Now you should be able to resign APK files even faster!
The second tool is the so called Cert-Checker. Read more