Error when opening Chrome on Android 13 via adb

OK1 Comment

Recently I’ve started adapting our test framework for new Android release, and encountered an unexpected error when opening Chrome on Android 13 via adb. Since solving this issue required some investigation and a knowledge of Android development, I’ve decided to write a blog post about it.

TL;DR: Use the correct command below to launch Chrome:

adb shell am start -a android.intent.action.VIEW -d https://google.com -n com.android.chrome/com.google.android.apps.chrome.IntentDispatcher --es "com.android.browser.application_id" "some_package"

And to launch Samsung browser:

b shell am start -a android.intent.action.VIEW -d https://google.com -n com.sec.android.app.sbrowser/com.sec.android.app.sbrowser.SBrowserLauncherActivity --es "com.android.browser.application_id" "some_package"

Those, who want to know all the nitty gritty details, please keep reading.

Continue reading →

Most common test automation mistakes – Part 2

OK

Note: This is Part 2 of a two-part series on most common test automation mistakes. Part 1 is here.

This is my take on the “most common test automation mistakes” topic. However, I’m not going to delve into the mistakes SDETs make when creating test automation strategy or using Selenium etc. Instead, I’m going to concentrate on mistakes on a coding level, which are relevant to many testing tools, frameworks and programming languages.

Continue reading →