Daniel Knott has used a variety of different programming languages and software quality assurance tools. He has been working on software development and testing for seven years, and since 2010 he has been working for Xing AG in Hamburg, Germany, and in several projects, such as Xing Survey and Xing advice, he is responsible for test Management, testing his own initiative and test run. Daniel is now the quality Assurance team leader in the Xing Mobile and Xing API team. In the Xing Mobile team, he is also responsible for Xing the test management and testing of Android and iphone apps. Daniel has extensive experience in software testing of tools like Robotium, KIF (Keep It functional), Selenium and Java. He also made presentations at various agile conferences and posted them regularly on his blog and Xing blog.
Pressure test and interrupt testing are important parts of the mobile test. With the help of tools, the mobile tester can determine the performance or stability issues that the app may have. To test your app's interruptions, you can manually trigger multiple notifications for your device when you use the app. Notifications can be messages, calls, app upgrades or push notifications (software interrupts). Press the volume to increase or decrease the button or any other hardware button is an interruption that will affect your app. Manual completion of all tasks means that the workload is very large and time-consuming. In most cases, those test scenarios cannot be completed manually, because it is very difficult to simulate high-speed and multi-user input with just one or two hands. But with tools it's easy to finish, and it's easy to integrate into the development and test process.
Android Monkey Tools
For Android apps, you can use the Monkey[mon01] tool, which is the Android software Development Kit (SDK). The monkey tool can be executed on a physical device or emulator. At execution time it generates virtual random user events such as touch, click, rotate, bash, reduce volume, turn off network connection and so on to the app to stress test, see how the app handles all of these inputs and interrupts. You need the install package name of the Android APK file to execute the Monkey tool, otherwise the tool will execute its random command for the entire phone instead of just the app. With the app code, you can find the installation package name in the Androidmanifest.xml. Assuming that only a compiled APK file is available, the mobile tester can use the Android Asset Packaging tool [AAP02] (AAPT) to get the installation package name from the app. AAPT is located in the Build-tools directory of the installed Android SDK. The path to the AAPT is as follows:
Use the following command to read the installation package name from the APK file.
The input will look like the following:
Assuming you have the installation package name (Com.myapp in this case), run monkey with adb (Android Debug Bridge) [ADB03]. The following command will start Monkey:
2000 shows the number of random commands that monkey will run on the app. With an additional number of parameters, monkey will generate the same sequence of events again. It is really important to reproduce a bug during the monkey run.
UI Automonkey Example Script
If you write a script, you can stress- test your iOS app in Xcode. At the end of the test execution, both tools generate an overview of the errors or problems that may occur in the app.
Note: specific installation instructions and complete example scripts can be found on the tool manufacturer's site.
Both tools can be integrated into a continuous integrated system to proactively execute after each command. Stress and interrupt testing for mobile apps is fairly straightforward and should be part of the mobile testing strategy. In addition, it will have a huge benefit to the tester and help the team build a stable and reliable mobile app.
Copyright notice: This article from SPASVO Software Testing network: http://www.spasvo.com/news/html/20141112144940.html
Original works, reproduced when you must be in the form of hyperlinks to the original source, author information and this statement, or will be held liable.
App pressure test Beginner Tutorial