Geek Answers Handbook

Testing the life cycle and recovery of Android application applications when an empty process state is reached

Recently, I tried to improve my knowledge and skills regarding the management of the state of Android applications at different points in the application life cycle. In particular, I tested various ways to maintain and share global data between actions . In my test applications, in order to test the recreation of global application data and / or singleton data, I need to wait several hours or more so that my phone decides that other processes are more important and put the test application in the empty state of the process, as defined in the life cycle documentation the process. At the moment, these applications are freed up and need to be recreated as soon as the application is again brought to the fore. If done incorrectly, reinitializing the last known state of the application can lead to a force that is close for various reasons.

So my question is that, not expecting this to happen organically, there is a real world to test for this event. For example, what does a QA use case look like that checks an application that enters the background for a (very) extended period of time and then comes to the fore again after the application has reached the state of an empty process?

+4
source share
1 answer

:

, . . " " - , , .

, , . :

  • .
  • "", .
  • 3- ( Facebook, Youtube Google Play ).
  • .
  • , 3 , .

/ , .

P.I.T.A., .

+3

More articles:


All Articles