Effective Screenshot Capture in Android Black‑Box Testing Using ActivityController and ProcessObserver

The article introduces common challenges in Android black‑box testing for capturing useful screenshots and proposes three main approaches: using third‑party screenshot services, implementing a custom Shell service started via app_process, and employing ActivityController to monitor activity changes.

It recommends a custom Shell service because it continues running even if the test script crashes and works on Android R and later where uiautomator 1.0 is no longer supported. The service records screenshots on activity changes, process state changes, and app crashes or ANRs.

To capture activity changes, the article shows how to register an IActivityController implementation:

IActivityController mActivityController = new IActivityController.Stub() {<br/>    @Override<br/>    public boolean activityStarting(Intent intent, String pkg) throws RemoteException { return true; }<br/>    @Override<br/>    public boolean activityResuming(String pkg) throws RemoteException { return true; }<br/>    @Override<br/>    public boolean appCrashed(String processName, int pid, String shortMsg, String longMsg, long timeMillis, String stackTrace) throws RemoteException { return false; }<br/>    @Override<br/>    public int appEarlyNotResponding(String s, int i, String s1) throws RemoteException { return 0; }<br/>    @Override<br/>    public int appNotResponding(String processName, int pid, String processStats) throws RemoteException { return -1; }<br/>    @Override<br/>    public int systemNotResponding(String msg) throws RemoteException { return 0; }<br/>};

The article also discusses drawbacks of ActivityController, such as interference when multiple processes register the service and the inability to detect fragment switches.

To complement ActivityController, it introduces IProcessObserver for monitoring process lifecycle events, providing code:

IProcessObserver mProcessObserver = new IProcessObserver.Stub() {<br/>    @Override<br/>    public void onForegroundActivitiesChanged(int pid, int uid, boolean foregroundActivities) throws RemoteException { /* handle */ }<br/>    @Override<br/>    public void onProcessStateChanged(int pid, int uid, int importance) throws RemoteException { }<br/>    @Override<br/>    public void onProcessDied(int pid, int uid) throws RemoteException { }<br/>};

Both services are combined into an integrated workflow: ActivityController detects page changes, IProcessObserver validates them, a timer captures screenshots every 2 seconds, compares the new bitmap with the previous one using image similarity (threshold 0.8), and re‑registers the ActivityController if no updates occur within 5 seconds.

For rooted devices, the article presents a special method using the Linux getevent command to read raw touch events (e.g., ABS_MT_POSITION_X/Y, BTN_TOUCH) and derive click or swipe actions, which can then trigger screenshot capture and optionally draw the event trajectory on the image.