IssueTracker

Component used: lifecycle-process
Version used: 2.0.0
Devices/Android versions reproduced on: Robolectric 4.3

I initially filed this with Robolectric, but it looks like the root cause is in the ProcessLifecycleOwner class.

This class is a singleton, and its state isn't reset across tests. The consequence is that an app which queries ProcessLifecycleOwner's lifecycle state may not have the expected value when multiple tests are run sequentially.

Sample project here: https://github.com/libon/ProcessLifecycleOwnerPersistedState

A specific example (detailed in the sample project), is that if at the end of test1 the ProcessLifecycleOwner's lifecycle state is RESUMED, it will also be RESUMED at the beginning of test2, which is unexpected (we'd expect the state to be CREATED at the beginning of the test, before any activity is launched).

Note: not sure if this is related: https://issuetracker.google.com/issues/115687653
Note: robolectric issue: https://github.com/robolectric/robolectric/issues/5080