ProcessPhoenix
ProcessPhoenix copied to clipboard
Create an automated testing strategy
trafficstars
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.
Maybe the new Android Jetpack Navigation Architecture Component can help identify or enforce the activity stack?