In one of my last posts I published my mobile testing cheat sheet. The reactions I received from social media and other channels was just great. The cheat sheet was very well received by you and I think it will help you to not forget the important parts when it comes to mobile app testing.
Maybe you have read my blog series about smartwatch app testing including the different watch platforms as well as several testing ideas that might help you to tackle this new technology stack. Wearables and especially smartwatches are becoming more and more important in our life and may be the next big challenge for you as well. Eran Kinsbruner wrote a great guest blog post about wearables in 2016 and if you miss that post I highly recommend you to read it here. The post will provide you with lots of useful insights in the wearable world. Read more
My latest eBook Smartwatch App Testing is now available on leanpub.com. The book covers the smartwatch platforms Tizen OS, Pebble OS, watch OS and Android Wear. Next to the platforms the book describes the 4 key areas of smartwatch app testing, more than 45 testing ideas as well as a smartwatch app testing cheat sheet.
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 is the 4th and last post of my smartwatch app testing series. However, there will be one more post with lots of testing ideas coming next week, so stay tuned for that. In this post I will write about Android Wear and the important features to know about this platform. Android Wear, as the name already suggest is based on Android and is developed by Google. The platform was launched at the Google I/O 2014.
Android Wear is written in C, C++ and Java and is open source like Android. The latest version based on Android 5.1.1 aka Lollipop (Version 6.0.1 aka Marshmallow is currently in roll-out stage). Since Android Wear is open source many manufacturers already produced their own Wear based watches. Some of you might think, yet another fragmentation challenge is coming up, but this is not the case for Android Wear. Google build this platform in a way that the UI is not customizable like Android for smartphones. The main goal is to get a common look and feel as well as features on different watches, produced by various manufacturers. This is a great step for all people working with wearable apps based on Android Wear, because it downsizes the amount of work. Read more
This is the third post of my smartwatch app testing series and in this post I will write about Pebble OS. In the previous posts I wrote about Tizen OS and watch OS. I think we all know the Pebble watches from their success on the Kickstarter campaign in 2012. In this campaign the company Pebble Technology Corporation raised more than $10 million dollar which was the best Kickstarter project at that time. With the raised money the company was able to produce the first Pebble watch. Since then, Pebble launched different versions of their smartwatches and the concept is different compared to Tizen, watch OS or Android Wear. Pebble’s characteristic is the low power e-ink display with either 2 or 64 colors. Right after the start of the first Pebble and the Pebble OS, this platform has become more and more attractive in the smartwatch business and therefore it is important to know the platform details in order to develop or to test for this system.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.