Is there a way of testing the save and restore state code of an activity programmatically ? I mean doing this :
How to test code built to save/restore Lifecycle of an Activity? but in an automated way.
I have tested activity.recreate()
method which is almost what I am searching, but in fact it does not reset the fields of my activity like if I was killing the process. So my test can pass even if I don't implement the restoring things in my onCreate
method (since my fields are unchanged...).
I am currently playing with Espresso v2 and I was wondering if this could be possible maybe by playing with the InstrumentationRegistry.getInstrumentation()
?
The solution is to use the
activity.recreate()
method BUT do not forget to follow this by an assertion which waits for an idle state. My problem with my first attempt was that the test I was writing was like :Where
XXX
was a field that I expected to be null when no save/restore state handling had been implemented. But that was not the case because my assertion was not waiting for the recreation task to be completed.So in my situation, my problem was solved when I simply add an espresso assertion which does the job, for example by verifiying that the TextView which displayed the
XXX
field was empty.Finally, thanks to the UI thread synchronization provided by Espresso, my test which can assert on my activity save/restore state missing implementation can be written like :
Note that the rotation solution suggested does the job either, but can be much slower than
activity.recreate()
when we just want to test the activity lifecycle. And in my case it was not relevant since my activity was not implemented for a landscape orientation.You can rotate the screen and verify that the state is saved and restored properly.
Full example: http://blog.sqisland.com/2015/10/espresso-save-and-restore-state.html