I suspect we could probably add a test to tscroll that does this.

making this block our android meta bug because I imagine we would want this before shipping to release

Botond, do you have any ideas for how to drive an async zoom programmatically?

Something like this.

Or, if you prefer, via double-tap.

Can we do this using Raptor or do we need Talos for this?

The perftest team currently has no plans to run Talos on android.

I'm not too familiar with either, but based on a brief conversation with Markus, it should be doable with Raptor (e.g. we should be able to access APIs like the ones mentioned in comment 3 / comment 4 in a Raptor test).

Markus suggested reaching out to :jmaher about details about how Raptor tests work.

@botond: With async zoom coming to desktop as well, does it make more sense for this to go to the APZ component instead of wr-android?

I think we'll want performance tests on both mobile and desktop, as they have different performance characteristics (due to e.g. different screen sizes, different levels of device power). That could however take the form of running the same test on multiple platforms.

I don't feel strongly about which component we track the bug in.

Guessing we can close this now?

Did we end up writing any tests in this area?

If not, I think it's worth keeping this open (but we can move it into Panning and Zooming, as the purpose of the test at this point would no longer be anything related to rolling out WebRender, but rather to ensure pinch-zoom performance doesn't regress in general going forward).

I don't think we wrote any tests.