The documentation at https://chromium.googlesource.com/chromium/src/+/master/docs/android_test_instructions.md is also out of date.

What is the recommended way to test things on android for those without access to a device?

#1: are you referring to https://chromium.googlesource.com/chromium/src/+/master/docs/android_test_instructions.md#emulator-setup specifically?

The (bad) answer to your question: at the moment, I don't think there *is* a recommended way to test chromium things locally w/o a device.

I am not likely to have time to work on this in the near- or medium-term. Releasing it to reflect that.

Re#2: Yes, that's what I was referring to.

I'll up the priority in the hopes that someone will pick this up. This used to work, and it's quite sad that we didn't care to update this when the SDK was updated.

Sad, perhaps. That doesn't make this a P1 for I>C>A, though.

The Chromium bug guidelines (https://www.chromium.org/for-testers/bug-reporting-guidelines/chromium-bug-labels) mentions that all regressions should be P1.

This also blocks testing things on Android unless you have an available testing device. I'll leave it up for your discretion, but I think this should be P1.

Chiming in to point out that we were using those instructions on the Chromecast team as well. Currently, I'm using the install_emulator_deps.py and avd.py from an old version of the source from before the sdk was updated, which works for our purposes.

I believe that'd be regressions in the browser.

We've kept the script alive for the last few years with, AFAICT, minimal usage (to wit: see the interactions w/ this bug since it was filed three months ago). Given the low usage and that most chrome+android devs and all of our bots have physical devices, this simply isn't important enough to merit being a P1 for the team. That's not to say we wouldn't like emulators to work; it's just not a particularly high priority for us at the moment.

#6: interesting...

Moving Infra>Client>Android -> Infra>Client>Chrome+OS=Android

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot