We could add a crash test for bug 1850480 that would mirror the provided steps to reproduce and then assert the running app lifecycle *. * In Espresso, there’s no direct way to check if an app has crashed because the testing framework operates within the same process as the app being tested. This means that if the app crashes, the testing process will also be terminated, and you can’t catch this event or assert it in your test
Bug 1852759 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We could add a crash test for bug 1850480 that would mirror the provided steps to reproduce and then assert the running app lifecycle [*]. [*] In Espresso, there’s no direct way to check if an app has crashed because the testing framework operates within the same process as the app being tested. This means that if the app crashes, the testing process will also be terminated, and you can’t catch this event or assert it in your test
We could add a crash test for bug 1850480 that would mirror the provided steps to reproduce and then assert the running app lifecycle [*]. [*] In Espresso, there’s no direct way to check if an app has crashed because the testing framework operates within the same process as the app being tested. This means that if the app crashes, the testing process will also be terminated, and you can’t catch an event or assert it in your test AFAIK.