if a webview dump times out, normally it's already in a bad state,
throwing runtime execption will generate a crash on the test case
and make the test move forward.
Change-Id: Id7430700db6b6d90160d60d23debd250b1731789
Currently test code use getActivity to get DRT's assets. However
the side effect is that this will actually launch the activity.
This is not affecting any tests yet, however there are cleaner
ways to do this. The instrumentation framework provides a
getTargetContext call which will give access to app under test's
context, and therefore granting access to its assets.
Change-Id: I0560b0fa5681f80bcb9296beec3fd0549c40cc8e
This fails beacsue the result of the test is so large that DRT suffers
OOM when reading the result. This will be fixed when we switch to
DRT2. Skipping for now to keep the crashes at zero.
Also fixes bug numbers for other skipped tests
Bug: 2697589
Change-Id: I897ff1f0a2941d305af5fb1c8de8f6690365fb9e
This is required for tests that test PageCache behaviour, eg
- fast/dom/DeviceMotion/no-page-cache.html
- fast/dom/DeviceOrientation/no-page-cache.html
- fast/dom/Geolocation/no-page-cache.html
Change-Id: Ie5862f6c86718142c949be81a85358ca6fac628a
Since the UI uses multi-touch for zooming, the event is passed to webkit
only when the webpage doesn't allow zooming.
1. Updated the data structure TouchEventData in WebViewCore.java
to take multiple points and used it everywhere.
2. Added a passMultiTouchToWebkit() function to do what its name means.
3. Added the multi-point touch support to dumprendertree.
Change-Id: Iafc1aa7b21a587ad26efd2f124b9a66316297ab8
this test crashes on Passion, and runs webcore into a bad state on
Stingray. To make sure it does not block the entire layout test
suite on Stingray, skipping this test for now.
http://b/2982500
Change-Id: Id4875112705df9b2c5b003a2c32c292765ab17fc
Merge commit '1c045003788725b40af5489149ac0fc8bfebb1ea' into gingerbread-plus-aosp
* commit '1c045003788725b40af5489149ac0fc8bfebb1ea':
add mouse up/down/click support in DumpRenderTree
This patch modifies the old-style hard-coded ignore list. The new-style
text file (in external/webkit/LayoutTests/platform/android) has been
modified separately, as part of the normal WebKit merge process.
Test added in http://trac.webkit.org/changeset/64613
Needs clearAllApplicationCaches() callback. See http://b/issue?id=2944196
Change-Id: I31655c363c93eada40d01123e9c14c0d03bdba7b
This merge introduces two new Geolocation tests that to pass we need
a new LayoutTestController function. We ignore those tests until this
function is added - see b/2914450
Change-Id: If13dda2caa467b771d4a21d60463319019cc7679
A previous change terminates page load if there's certain JS errors;
the intention was to speed up layout tests such that page accessing
non-existent test controllers/methods will get immediate termination
instead of waiting on timeout. However this causes problem for page
cycler because it may interrupt the test run too early. Also there
was a bug on bracketing on the termination conditions (operator
precendence issue).
Change-Id: I2f19e48fa0061286fddf0f7cbb4953d7f7d88f76
Remove the overridden WebChromeClient.onProgressChanged function. We don't seem to need it and
it appears to be the cause of b/2681943. Without that code we need to tweak the terminating
conditions in onPageFinished and notifyDone.
Change-Id: If2958007d92f2da92ae0de19eb07a0b38258fae0
- Make the layout test counter work when you run tests through the GUI
- Use the progress bar in the applications title bar to display test progress
Change-Id: I3d4b778470e812b80b7a64297b3a64ba6f9d083c
This fixes a bug in commit https://android-git.corp.google.com/g/#change,52518.
Updated index to be zero based when passed around and off by one error on
resume. Note that previous commit changes how DumpRenderTree dumps titles.
This might affect the results of layout tests.
Change-Id: I3d6989d71c336f90168e38c994dd36743bda365c
