commit cfae5009533f60bdd95b48b54db10987cd1a499f
author Brian Muramatsu <btmura@google.com> Wed Dec 22 14:21:44 2010 -0800
committer Brian Muramatsu <btmura@google.com> Wed Dec 22 14:24:13 2010 -0800
tree f2503f0e8b05d5c1ec088a4b052c9028f44062d9
parent 73da8539b16c43ce8155ccfc98a0cfa69ed35a77

Fix InstrumentationTest#testSendPointerSync

The test sends a motion event with a coordinate of (50, 50). This now ends
up being absorbed by the ActionBarView's LinearLayout. Change the
testing coordinate to (100, 100)...

Change-Id: Ibbbe02657bbb99b5db1f41948b7d5a2ba5f97ceb

tests/tests/app/src/android/app/cts/InstrumentationTest.java

diff --git a/tests/tests/app/src/android/app/cts/InstrumentationTest.java b/tests/tests/app/src/android/app/cts/InstrumentationTest.java
index 12baed5..69090e1 100644
--- a/tests/tests/app/src/android/app/cts/InstrumentationTest.java
+++ b/tests/tests/app/src/android/app/cts/InstrumentationTest.java
@@ -73,8 +73,8 @@
         final long eventTime = SystemClock.uptimeMillis();
         // use coordinates for MotionEvent that do not include the status bar
         // TODO: is there a more deterministic way to get these values
-        final long x = 50;
-        final long y = 50;
+        final long x = 100;
+        final long y = 100;
         final int metaState = 0;
         mMotionEvent = MotionEvent.obtain(downTime, eventTime, MotionEvent.ACTION_DOWN, x, y,
                 metaState);