If you have implemented many automated tests with Robotium, you will notice that Robotium is not the fastest tool when it comes to test execution time! Especially in big projects with more than 100 automated Robotium tests the execution time is really long (>1h). For nightly regression testing this is not a problem, but If you want to know if a simple commit from a developer break something, executing the whole test suite is not very efficient. To get a much faster impression of the quality of the last commits, you can build for example a smoke test suite. This suite covers the basic functionality like login, clicking on important entries but not all edge cases, like a full regression test suite will do.
How Tos
Kindle Fire Tablets Pre-Submission Assessment Guide
Today, Amazon send an email to all Amazon App Store developers who have already an app in their store. This email included also a link of a Pre-Submission Assessment Guide where developers find hint and tipps how to test their app for the store. The list is a nice overview of possible things that should be tested during development and before submission. Also a short test example is provided! Good for developers who have no own QA, for QA people this list is not enough ;).
How to Use This Guide
For each app you intend to submit, follow the instructions in each of the following four test groupings and note the behavior. If your app does not pass the assessment criteria listed below, you should fix any of the issues found before submitting your app for final review.
…
Robotium, Jenkins and Ant
I think it is time for a new How to/ Tutorial on my blog. Today, I want to give you an overview of how to setup your Robotium test project to build it with the tool Ant. If the project is configured for Ant, I will explain how to integrate it into the continuous integration server Jenkins. With the combination of the build tool Ant and the CI Server Jenkins, you are able to build up your own mobile test automation environment. Written Robotium tests can be executed on schedule or directly after a developer commits new code to the repository.
Useful Android Development/ Testing Tools powered by troido
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.
iPhone test automation using KIF (Keep It Functional)
In my last posts I dealed a lot with Android and how to implement automated regression tests using tools like Robotium. This post describes how to implement automated tests using the tool KIF (Keep It Functional, http://corner.squareup.com/2011/07/ios-integration-testing.html). KIF is an open source test framework developed by the company square (https://squareup.com). It is an iOS integration test framework that allows you to implement test cases with objective C that can be executed currently only against the iPhone/ iPad simulator. The KIF tests are integrated to your workspace, there is no need for additional servers or services that must be started.