Android Testing Movement Problems on diverent devices
Posted: Tue Sep 10, 2013 2:04 pm
Hello Guys,
i followed the api and searched for some functions for the ScrollView Movement.
At first i wrote some code to check if this 3 functions work...
This Code worked for the "Samsung Galaxy s4" sufficiently. It may scroll but the main problem is... it won't stop at the TouchEnd function and continue scrolling so i filled the Code up with a Delay...
That code was perfect for the "s4", so i tried the same Code on the "Nexus 7".
Now he haven't scrolled. He just touched and didn't moved. I builded a workaround for this.
This interrupted the scrolling-action and should make it possible to make a screenshot. After this worked sluggish i decided to take some more devices and test my code on this devices. I tried this code on the "Desire S" and the "Samsung Mini". On both devices the code shown some strange reactions. I activated the developing tools from the smartphones to have a closer look about the forced actions. After starting the test run i've seen the action and could follow the automatisation steps. The main problem on these devices is that despite the action is forced nothing happend. I see how he touches the location, see how he moves to the top, see how he end his touch on the top. But the application isn't scrolling.
I tried this tests on some other devices and i've got the exact same result.
Now here are the questions:
Is there any possible functions or API-Elements to scroll safely? Is there any possible functions or code snippets that checks if the end of an webView-element (android-element) is reached (Scrolling Down/Y-coordinade/Blue-Overscrolling-Gradient) if the normal way for checking the y-choordinade isn't possible?
i followed the api and searched for some functions for the ScrollView Movement.
At first i wrote some code to check if this 3 functions work...
Code: Select all
articleViewPager.TouchStart(Location.LowerCenter);
articleViewPager.TouchMove(Location.UpperCenter);
articleViewPager.TouchEnd(Location.LowerCenter);
Code: Select all
articleViewPager.TouchStart(Location.LowerCenter);
articleViewPager.TouchMove(Location.UpperCenter);
Delay.Milliseconds(200);
articleViewPager.TouchEnd(Location.LowerCenter);
Now he haven't scrolled. He just touched and didn't moved. I builded a workaround for this.
Code: Select all
articleViewPager.TouchStart(Location.LowerCenter);
articleViewPager.TouchMove(Location.UpperCenter);
articleViewPager.TouchEnd(Location.UpperCenter);
if(deviceName == "Nexus 7"){
Delay.Milliseconds(20);
articleViewPager.TouchStart(0,50);
articleViewPager.TouchMove(0,60);
articleViewPager.TouchEnd(0,60);
}
I tried this tests on some other devices and i've got the exact same result.
Now here are the questions:
Is there any possible functions or API-Elements to scroll safely? Is there any possible functions or code snippets that checks if the end of an webView-element (android-element) is reached (Scrolling Down/Y-coordinade/Blue-Overscrolling-Gradient) if the normal way for checking the y-choordinade isn't possible?