Home » Android

Category: Android

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.

#HappyTesting

Featured Image Source: https://www.flickr.com/photos/mom2sofia/8393131475
Android Resources

List of Android Development Resources – Guest Post

Are you an Android developer or app tester? Do you want to learn from or get connected to other peers in the Android community? If so, there is something useful you should read and check out.

Andreas and Jessica from AnySoftwareTools, recently created a big list of Android development resources. The list covers a wide range of materials including blogs, tutorials, forums, podcasts, and social media communities. Whether you are new to Android programming, or you are a veteran who’s managed to develop an app, you’ll love this resource.

You can read the comprehensive resource here: http://www.anysoftwaretools.com/best-android-development-resources/

The list includes 46 blogs and tutorials, 11 forums and Q&A websites, 12 YouTube playlists, 5 podcasts, 10 Google+ communities, 11 Facebook groups, and counting. Did we miss any resources you like but not mentioned there? Let us know, we will be happy to consider adding them. That’s the value of keeping a resource updated, isn’t it?

Anyway, check it out and let us know what you think. If you like it, feel free to share it out. Happy reading and coding!

About the author
Jessica Carrell is a technology enthusiast who founded AnySoftwareTools with several geek friends. When she is not coding or writing tech stuff, she loves shooting photographs behind her camera lens.

Image Source: https://stocksnap.io/photo/QVKE96OD36
How to Build Your Own Android Device Cloud - Adventures in QA

How to Build Your Own Android Device Cloud

In this post I will describe how to build your own Android device cloud in the office. You may think this is expensive and will take lots of time and work, but I promise it isn’t. After installing the device cloud you are able to control the real Android devices from your web browser no matter how far you are away from the real device. For all iOS testers and developers out there, I must say sorry, this post is only handling Android devices until know the tool I will use is not supporting iOS. Before I get started with the installation and setup I list shortly the hardware and software I used to setup the whole system.

Hardware and Software

Lets start with the software that is managing the Android devices. The software is called openstf, where STF stands for Smartphone Test Farm. The software is open source and is maintained by Simo Kinnunen and Günther Brunner. STF offers a plethora of really cool features like Read more

Accessibility Scanner

Google just released a new Android app that helps you to identify accessibility problems in your Android app. The app is called Accessibility Scanner and can be downloaded from Google Play. Once the app is installed on your test device, it will guide you through the setup process, to activate the scanner in the accessibility settings of the phone.

Accessibility Scanner Settings 1 - Adventures in QAAccessibiltiy Scanner Settings - Adventures in QA

 

 

 

 

 

 

 

When the setting is active you will see the blue accessibility scanner app button on your home screen of the device (floating button). Read more

[Reblog] Android Smartphone Test Farm

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.

Our challenge

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