Create an automated testing strategy

Since this deals with process death an instrumentation-based test won't work. Maybe UI automator or UI automation could be used to drive the sample app. We can use the displayed process ID for asserting a new process is created. How do we assert against the activity stack, though?

At worst, a simple script which interacts over `adb` and dumps activity/process info and does text-based verification would work. But that's last resort.

The issue names no source file or existing test; start by locating the sample app and its current test setup. Compare UI automator or UI automation with an adb-based script, using the displayed process ID and activity/process dumps as the stated verification points. Done requires an agreed strategy for process recreation and activity-stack assertions.

Written by the indexing model from the issue text.