Issue with SplashScreen about robotium HOT 6 CLOSED

From [email protected] on November 05, 2010 05:07:39

Correct activity did not appear. expected:<...Splash...> but was:<...Home...>

I guess that the Activity that is opened after the splash screen is <...Home...>?

Owner: renasreda

from robotium.

From [email protected] on November 05, 2010 05:14:10

Exactly. I know that using a sleep is not good but I would like to know why this test fails.

Some questions:

• When is solo.assertCurrentActivity executed?
• Leaving the UI thread alone will fix this issue?

from robotium.

From [email protected] on November 05, 2010 05:34:24

It gets executed after the Home activity is active. By the time assertCurrentActivity() gets executed the Splash activity is no longer active. Usually the problem is the opposite. Please see this thread: http://groups.google.com/group/robotium-developers/browse_thread/thread/79a70038c16e35e6/f08a0d9733982a59?lnk=gst&q=getCurrentActivity#f08a0d9733982a59 In both cases there is unfortunately nothing we can do about it. It takes some time for Robotium to load and the activityMonitor to start registering a new Activity. If a new Activity is not registered then it will think that it is still on the Splash activity. In your case the sleep() prevents that and gives time to Robotium to register the new Home activity before assertCurrentActivity() is executed.

Thanks for reporting this. As I said earlier this is a known limitation which we can not do anything about.

Status: WontFix

from robotium.

From [email protected] on November 05, 2010 05:49:46

renasreda: Thanks for your reply.
What would you recommend? Leave the SplashScreen untested?

Thanks.

from robotium.

From [email protected] on November 05, 2010 05:53:57

Yes, that is what I would do. I would use assertCurrentActivity() on the Home activity instead. And then take it from there.

from robotium.

From [email protected] on November 05, 2010 06:05:46

Cool, thanks for the support.

from robotium.