Time flies, my book Hands-On Mobile App Testing was published in the printed edition one year ago. Since then so many people wrote me via mail, twitter, facebook, XING or LinkedIn that they like the book and that they found it really useful. This kind of feedback feels really good and makes me happy.
In June last year I posted the following picture on twitter after I received a huge box of books :). Read more
If you are working as mobile tester in an Android team or you are an Android developer you know the pain of installing apk files to your test devices and you should have a look at ADB idea, which may solve your pain. Next to installing or uninstalling apk files from test devices, it is somethings necessary to kill your app, start it or even to clear the app data in order to have a fresh version of it. Usually you are using the known adb commands for that and execute them in the console or you open the device settings to clear the app data. However, this is time consuming if you are doing this several times a day.
If you are using Android Studio or Intellij IDEA you can use a very nice plugin called ADB idea to speed up your testing and development time. ADB idea is written by Philippe Breault and can be installed via the IDE plugin section, e.g. Preferences/ Settings -> Plugins -> Browse Repositories or you can download it manually from the JetBrains plugin page and install it via Preferences/ Settings -> Plugins -> Install Plugin from disk. Read more
In the previous posts you have read and hopefully learned something new about Tizen OS, watch OS, Pebble OS, Android Wear and what is important to know when start testing on one (or more) of those mobile platforms. Smartwatches may not be on everyone’s wrists yet, but that time can change very quickly in the next upcoming months and you must be prepared for the new way of interacting with your apps and devices. As you have seen in this series, smartwatches offer a complete new set of interactions, features and challenges for mobile testers and developers. The guys from gizmag did a great job in comparing the different smartwatch platforms from a software and hardware point of view and is a nice summary to the watches I used for this series.
However, the last post in the series is about smartwatch app testing ideas. Before I go into the smartwatch app testing ideas I want to briefly remind you about the 4 key areas of smartwatch app testing.
This post is a reblog from the XING developer blog. In the last week we had our quarterly HackWeek at XING. During the week I was working with some colleagues on a project to setup a Android Smartphone Test Farm based on openstf.io.
Excerpt from the original version:
Mobile is becoming increasingly important for companies that build web applications, and that also includes XING. Over 50% of our platform traffic comes from mobile devices. This in turn leads a constant increase in the complexity and amount of testing work required on mobile devices.
At the beginning of 2015 XING launched a new internal initiative called “Unleashing Mobile”. The idea behind it is to upscale mobile development from a single mobile team to multiple teams within the company. The previous team setup was simply not able to keep pace with the development speed of the web platform and bring more and more features to the Android, iOS and Windows Phone mobile platforms. As things stand, we have 5 mobile feature teams developing features like profile, jobs, content or messages. Besides that, each platform has a central core team divided up into a platform and framework sub-team. The core platform team works on features that haven’t yet been passed on to the domain teams. As well as building its own app features, the core team has adopted more of a consulting role in helping to keep the whole app consistent and clean. Another key task of the central core teams is to integrate all of the code changes every two weeks to make sure that a stable app version can be released to our users. Read more
Lately I have been asked by Rosie Sherry the women behind Ministry of Testing, what are the main mobile challenges software testers need to face in 2016. Rosie asked me for only one testing challenge that we have to handle. In the first place the mobile device fragmentation came to my mind, but Rosie mentioned right from start, that this topic is already in the list. The next topic that came to my mind pretty quick is “In the Wild Testing”. And that is what I have written.
One of the biggest challenges software testers need to handle in 2016 is manual “In the wild testing”. The problem that I see, is that many software testers, test mobile applications in the same way as they would test web or desktop applications, always on the same place with the same Internet connection. But mobile apps are not the same like web or desktop applications. They are used in a total different environment with different Internet connections. If a mobile app is tested only with a fast and stable Internet connection lots of problems will not be covered during the testing and development phase. Read more