search

chchgb / android-crawler

Automatically exported from code.google.com/p/android-crawler
0 stars 0 forks source link

Session is not saved when the instrumentation crashes #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When the crawler crashes, or the jUnit method testAndCrawl() fails for any 
other reason, the remaining traces are saved from the session onto disk.

This doesn't happen when the application under test crashes and the 
instrumentation fails: the tearDown() method is never executed.

There should be another method called even when tearDown() is not called. 
Otherwise, we need a way to catch the exception thrown by the jUnit framework 
(very unlikely)

Original issue reported on code.google.com by nofatclips on 24 Oct 2011 at 9:39

GoogleCodeExporter commented 9 years ago 
Workaround: set Resources.MAX_TRACES_IN_RAM = 1

Original comment by nofatclips on 24 Oct 2011 at 9:41

GoogleCodeExporter commented 9 years ago

Original comment by nofatclips on 11 Nov 2011 at 7:39

GoogleCodeExporter commented 9 years ago 
As of r97 the session can be saved and restored by setting the ENABLE_RESUME 
parameter

Original comment by nofatclips on 19 Nov 2011 at 6:41