search

mozilla-mobile / perf-frontend-issues

A repository to hold issues related to front-end mobile application performance.
4 stars 0 forks source link

Document basics of performance testing (request from sparky) #155

Closed mcomella closed 3 years ago

mcomella commented 4 years ago

Sparky raised a concern that something is undocumented:

just a migration guide because testing on fennec vs fenix is quite different

Anecdotally, I've seen folks running into trouble updating the various tests to the schemes we use in fenix and I agree there's no central place to look to understand how to adapt to fenix.

Here are specific examples sparky has on what this guide might contain:

So for one, the activity changes. Next, for pageload tests we have to add new intents to get it to work: --firefox.android.intentArgument android.intent.action.VIEW --firefox.android.intentArgument=-d --firefox.android.intentArgument about:blank

Lastly, there are no fenix-specific prefs which is a large deviation from fennec. So we should specify that somewhere and mention the --ez performancetest true intent will likely solve the testing issues they may have (and mention the existing requirements that are required for it to work).

There's the glean telemetry too which can't be disabled and this should be mentioned somewhere so people don't waste time looking for solutions (assuming there are none).

Perhaps independently, it might be useful to have a brief page to describe the ways to start the fenix from the command line that best replicates user scenarios (e.g. clicking the homescreen icon, clicking a link in another app)?

Please get sparky to look it over after we're done to know if we hit the mark!

mcomella commented 3 years ago

Triage: we haven't had anybody ask for this recently so no rush; we should consider doing it with https://github.com/mozilla-mobile/fenix/issues/13470

mcomella commented 3 years ago

We haven't heard about this for a while – let's reopen if we hear about it again.