Takes more time to tap a field where there five or more textfields in a screen

[GoogleCodeExporter]

What steps will reproduce the problem?
1.

solo.waitForActivity(currentAct);
solo.clickOnMenuItem(menuItem); 
solo.waitForActivity(nextAct);
solo.enterText(0, AMOUNT);
solo.enterText(1, CARD);
solo.enterText(2, EXPIRYDATE);
solo.enterText(3, SSN);
solo.enterText(4, ZIPCODE);
solo.enterText(5, "testing");
solo.enterText(6, "testing field");
solo.enterText(6, "testing field");

For above list of text fields takes time to tap to enter the text, suppose if 
we have two fields it enter the same in blazing speed.

Above is the complete code

2.
3.

What is the expected output? What do you see instead?
It should be fastly enter data, irrespctive of no. of fields in the screen.

What version of the product are you using? On what operating system?
Robotium 3.0

Please provide any additional information below.

solo.waitForActivity(currentAct);
solo.clickOnMenuItem(menuItem); 
solo.waitForActivity(nextAct);
solo.enterText(0, AMOUNT);
solo.enterText(1, CARD);
solo.enterText(2, EXPIRYDATE);
solo.enterText(3, SSN);
solo.enterText(4, ZIPCODE);
solo.enterText(5, "testing");
solo.enterText(6, "testing field");
solo.enterText(6, "testing field");

Original issue reported on code.google.com by alpatisu...@gmail.com on 16 Jan 2012 at 10:24

[GoogleCodeExporter]

How long time does it take? If you enter text into 4 edit text fields, how long 
time does it take then? Which Android version are you using? Please give some 
more information. 

Original comment by renasr...@gmail.com on 16 Jan 2012 at 1:10

[GoogleCodeExporter]

Robotium takes 40-50 secs to tap and enter text in edit text fields. If you 
enter manually it takes less 20 secs. 

I'm using ADT 15 and Robotium 3.0

Original comment by alpatisu...@gmail.com on 17 Jan 2012 at 8:38

[GoogleCodeExporter]

This is due to an issue with Android 4.0. If you try your test cases on 
Gingerbread you will notice another behaviour. Unfortunately, nothing can be 
done from Robotium in order to get around the Android 4.0 issue. We can only 
wait for google to fix the issue. 

Original comment by renasr...@gmail.com on 17 Jan 2012 at 8:43

• Changed state: WontFix