Closed GoogleCodeExporter closed 9 years ago
My email is ymittova@estaxi.ru.
Original comment by kostyukh...@gmail.com
on 4 Sep 2012 at 5:50
Also, I have logged all my startup functions and I have seen, that command
"solo = new Solo(getInstrumentation(), getActivity());" is most of the time.
My startup method is:
@Override
protected void setUp() throws Exception {
super.setUp();
setActivityInitialTouchMode(true);
solo = new Solo(getInstrumentation(), getActivity());
}
Original comment by kostyukh...@gmail.com
on 4 Sep 2012 at 7:57
Thanks for reporting this. Is it possible for you to send me a sample app that
exhibits this problem?
Original comment by renasr...@gmail.com
on 4 Sep 2012 at 12:35
Yes, of course. But, we need some time for it. I'll send you it obligatorily.
Original comment by kostyukh...@gmail.com
on 5 Sep 2012 at 8:58
Great. You can just email it to renasreda@gmail.com.
Original comment by renasr...@gmail.com
on 5 Sep 2012 at 8:59
Original comment by renasr...@gmail.com
on 11 Sep 2012 at 2:51
We have created test application, but situation wasn't reproduced.
We assume that the reason of the bug is in our application, but not in
Robotium. We are starting refactoring and later we will have more information
about it.
Thanks for your supporting.
Original comment by kostyukh...@gmail.com
on 11 Sep 2012 at 4:38
how to write the code for TabHost? Which method of Solo will be call?
thanks.
Original comment by donglei....@gmail.com
on 11 Sep 2012 at 7:44
How to simulate a click on TabHost or TabSpec?
Thanks.
Original comment by donglei....@gmail.com
on 11 Sep 2012 at 8:09
Thanks for letting me know. Will open up again if issue is reproduced.
Original comment by renasr...@gmail.com
on 12 Sep 2012 at 12:53
Hello! I think we have known the reason of this problem. We used for tests 2
phones: Acer Liquid and Samsung Spica. So, Acer has a custom and specific
firmware. And Samsung Spica has a firmware, which is not created for this phone
model.
Two days ago we had bought a new phone - Samsung Galaxy Ace 2. And all tests
run succesfully on this phone and starts without any manual touch.
So, my suggestion is "the reason of this defect is custom firmware of phone".
Thanks for your support.
Original comment by kostyukh...@gmail.com
on 14 Sep 2012 at 7:56
Original issue reported on code.google.com by
kostyukh...@gmail.com
on 4 Sep 2012 at 5:49