Blog Review 2018 - Adventures in QA

Blog Review 2018

And soon we are heading into 2019 and as a tradition of my blog, I always take the opportunity to look back what happened in the last year. The year 2018 was different for me. In terms of blogging and working. I shifted my focus from writing on my own blog to other blogs to support them with hopefully valuable content.

Also as a tradition I like to share numbers about my readers, where there are coming from how many of you visited my blog and so on. However, I can’t deliver this information to you anymore. The reason is simple, thanks to new GDPR law in Europe, I removed ALL the tracking from the blog. I have no idea where you are coming from and how often you are here.

But that is totally OK for me and I think for you as well 😉.


My testing highlights for this year where the 3 conferences I attended as a speaker. One of my favorite testing conferences on this planet are the Nordic Testing Days in Tallinn.

Read more

Mobile App Launch Strategy

A Mobile App Launch Strategy

Releasing an app is not an easy process. Once an app is rolled out to the customers there is no way of rolling it back like on web platforms. Imagine a native mobile app as a good old burned CD that was shipped as a part of a magazine or hardware parts containing the drivers. Once it’s burned and shipped you can’t fix it. The same applies for native mobile apps. Therefore, a solid mobile app launch strategy is key to success for every company.

Before an app can be released it’s important to know all the technical information about the software development cycle. How many developers, testers (internal or external) are involved in the app development. How often will the app be released, what is the sprint cadence. Is there an internal or external beta testing community in place that can be used before rolling out the app to the customers? As a foundation for the release strategy this kind of information is important.

When the development cycle comes to an end it’s important to gather all the required release information from the product team. Every release should have meaningful release notes informing the user about the new release. The store descriptions must be updated as well images.

Before building the release candidate of the new app version, every team must execute the automated checks and see if they pass. Additionally, it’s recommended to perform a last exploratory testing session to see if all the critical parts and the new features are working as expected.

The last thing before going live is to check the release checklist. A checklist for a release must be in place to double check that nothing was missed out. Find out in my lastest blog post for applause what the release checklist is all about and what needs to be done in the post release monitoring.

Read the complete article here:



Mobile Testing Techniques

Mobile Testing Techniques to Know

“It works on my machine,” is probably the most frequent comment a software tester will hear from a developer once a bug has been reported. An expected reply from a tester would be, “Then back up your system. We need to deliver it to our customers, because our product is only working on your system.” We all know that software isn’t bug free and never will be. However, software testers should use their testing skills and techniques to find as many issue as possible. Especially with mobile testing, software testers need a variety of techniques to identify issues in different environments and scenarios before the customer will find them.

In my latest blog post for Applause, I described two important mobile testing techniques to know. The first one is interrupt testing and how to test for interrupts especially for push notification as well as system interrupts. The second described technique is input testing. Most of the mobile tester I have talked about this topic, they always mention the input testing via the touchscreen. True this is the most important input mechanism, but there is more to cover. Furthermore, I have mentioned more techniques that are worth to know.

Read the complete article here:


Mobile Testing Strategy

Three Steps for a Successful Mobile Testing Strategy

Mobile devices and mobile apps are everywhere these days. Customers are using mobile devices and apps to play games, listen to music, and work from wherever they are. According to TechBeacon, more than half of mobile users will delete an app if it is crashing, freezing, or showing too many errors. As those who work in the field of mobile testing know, a mobile testing strategy is the key to success for a high-quality app. But defining a strong mobile testing strategy isn’t that easy. Mobile testers are facing many challenges to solve. There is device fragmentation, user mobility, high mobile user expectations, and device-specific hardware functions just to name of view.

And the challenges don’t stop there for mobile testers. More and more apps are now able to connect to wearable devices and other IoT devices.

Defining a Mobile Testing Strategy

With the rising complexity of mobile testing, a mobile development team needs to define a mobile testing strategy. With the help of a tailored test strategy, a mobile team can focus on the most important parts to deliver a great app to their users. It’s fairly easy to define a mobile testing strategy that will help downsize the amount of work needed during the development and testing phases. All you need to do is to gather user insights, define user scenarios, and specify your mobile testing approach. If you want to know how to define your own mobile testing strategy in three steps, read my lastest blog post at the Applause blog.

Read the complete article here:


Testing App Bundles - Adventures in QA

Testing App Bundles

With the introduction of Android App Bundles at Google i/o 2018, Android developers are now able to upload the Android app as a so called bundle to the Google Play Console. Based on the app bundle, the Google Play Console is now in charge to optimize, compile and sign an APK file for each specific mobile device configuration. With this new mechanism not all resources like images or text translations are part of the APK which leads to smaller APK sizes. Besides that, developers don’t have to compile APK files to specific Android versions or devices. Furthermore, developers are able to add dynamic features into the App Bundle. This dynamic features can be excluded from the initial download for the users to minimize the download time and size on the phone. Once the dynamic feature is needed, the app is downloading it as an extension to the app. This is called dynamic delivery.

To get the full picture about Android App Bundles and how it works, please read this article.

Testing App Bundles

But let’s get back to the testing part for App Bundles. The good thing is, that the “old” way of testing an APK file is still valid. But if the app is going to support App Bundles, there are a couple of new challenges mobile tester need to handle. Mobile testers need to test, that the App Bundles are delivered to the specific device configuration e.g. screen size, Android OS version or the used device language. Depending on the app complexity and the customer device usage, this will increase the amount of test scenarios significantly.

Google offers a new tool called bundletool to support the testing activities on the local machine. It will generate APKs from the App Bundles.

Using the command

bundletool build-apks --bundle=/APPUnderTest/test_app.aab --output=/APPUnderTest/test_app.apks

will compile a container with the ending *.apks which includes all the apk configurations your app supports. After the APKs have been compiled you can install them with the command

bundletool install-apks --apks=/APPUnderTest/test_app.apks

for the specific connected device.

Testing App Bundles Via the Play Console

Once the different APK configurations have been tested locally, a mobile tester must perform the same tests via the Google Play Console, to see if the Play Store delivers the right APK configuration to the different devices. Google introduced the internal test track to support the testing activities for App Bundles. Once the internal test track is setup with the test accounts, a mobile tester can use the Play Store app installed on the phone to check, that the right app configuration is installed on the device.

Last but not least, mobile tester must perform the app update testing with App Bundles, too.


Featured Image Source: