Bugzilla

One of the use-cases/tests from https://bugzilla.mozilla.org/show_bug.cgi?id=1511347#c1 is: "Target app running in background."

Very early and coarse vetting seems to indicate that this might be possible/feasible, even in CI (but we need to be extra careful[0][1]) with something like the following:

Launch the (browser) app:

```
adb shell am start -n org.mozilla.firefox/org.mozilla.gecko.BrowserApp -a android.intent.action.VIEW -d https://www.mozilla.com
```
(of course, we'd do it with Raptor)

Send target app to the background/minimize:

```
adb shell input keyevent 3
```

[0] As with our other power-use measurement tests, running for 20+ minutes in CI, a piece, we don't want to introduce test/data instability, due to this feature.
[1] There are also warnings/cautions from our Android team, who note that this (app-in-background scenario) is susceptible and beholden too, Android's memory-pressure killing off backgrounded apps/processes.

One of the use-cases/tests from https://bugzilla.mozilla.org/show_bug.cgi?id=1511347#c1 is: "Target app running in background," with bug 1546741 and bug 1548689 addressing "Target app running in foreground."

Very early and coarse vetting seems to indicate that this might be possible/feasible, even in CI (but we need to be extra careful[0][1]) with something like the following:

Launch the (browser) app:

```
adb shell am start -n org.mozilla.firefox/org.mozilla.gecko.BrowserApp -a android.intent.action.VIEW -d https://www.mozilla.com
```
(of course, we'd do it with Raptor)

Send target app to the background/minimize:

```
adb shell input keyevent 3
```

[0] As with our other power-use measurement tests, running for 20+ minutes in CI, a piece, we don't want to introduce test/data instability, due to this feature.
[1] There are also warnings/cautions from our Android team, who note that this (app-in-background scenario) is susceptible and beholden too, Android's memory-pressure killing off backgrounded apps/processes.