From August 2021, new apps will be required to publish with Android App Bundle on Google Play, according to Google. What is Android App Bundle (.aab)? What is it different from Android Package file (.apk)? Does it matter when we test it on Appium? Yes, it matters. In short, we need to update our toolchain.

In this session, firstly I'll explain what is Android App Bundle. Then, I'm going through how to automate it with Appium. Finally, I'll cover how we test Android App Bundle with different languages.

------------------------------------------

[Update] QA during my session.

## Doesn't it affect the quality of android application by compressing android app bundle?
I'm not sure if I understand the question correctly, but bundletool is a google official tool and it just generate an APK set archive file from Android App Bundle.  I think Google also uses the bundletool in Google Play. So I think it is safe to use the bundletool.

## What version of appium did start supporting Android App Bundle?
Accoding to CHANGELOG, Appium supports Android App Bundle since version 1.10.0. https://github.com/appium/appium/blob/master/CHANGELOG.md#changes-in-version-1100-from-191

How your Appium tests working? Are they working well as you expect? If no, you've probably come to a right place! 

As some of you might know, E2E tests can be flaky. When an Appium test fails, most of the cases you'll start an investigation by checking an Appium log. For those who just started testing with Appium, an Appium log looks like a mass of string. This can be sometimes a barrier to continue E2E tests with Appium.

In this session, firstly I'll cover what Appium log consists of and some basic techniques how to investigate Appium tests with Appium log. Then, I'll share you where to find possible solutions/workarounds. In the end, I'll shed light upon one of the well known troubles on Appium testing and how to avoid the trouble.

Frameworks for hybrid mobile apps, such as React Native, Cordova etc, have attracted more attentions. One of the reasons is that those frameworks enable us to develop both iOS and Android apps with web technology. This is important, as not only it breaks technology barriers in terms of native apps, but also it enables us to share one codebase across platforms.

However, when it comes to E2E testing on hybrid mobile apps, it can be challenging. Most of the cases the problem comes from context we test. As long as we test hybrid mobile apps as a native app, locators can be complicated and  it is difficult to share one test case across platforms. In order to address the problem here, we need to switch context. i.e. we should test them as web 
apps as they developed with web technology.

In this session, firstly I'll explain hybrid mobile apps and how to test them with Appium. Then, I'll illustrate how Appium automate hybrid mobile apps. Finally, as a developer of test automation service, I'll show some edge issues related to automating mobile apps and their solution/workaround.