91102 2012-07-12 09:10:43 -0700 [Chromium] Support running Android-specific layout tests 2012-08-13 05:24:54 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 66687 1 leandrogracia webkit-unassigned abarth leandrogracia peter oldest_to_newest 667845 0 leandrogracia 2012-07-12 09:10:43 -0700 Perform the required changes to support the chromium-android platform in the test infrastructure so we can run Android-specific layout tests. 667863 1 abarth 2012-07-12 09:29:55 -0700 Can you give an example of an Android-specific LayoutTest? Typically, we'd just put the LayoutTest in the http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-android directory. 667866 2 leandrogracia 2012-07-12 09:35:07 -0700 (In reply to comment #1) > Can you give an example of an Android-specific LayoutTest? Typically, we'd just put the LayoutTest in the http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-android directory. I'm afraid I don't have anything ready to be uploaded yet, but I mean any layout tests that work with WebKit API features that are guarded by the ANDROID macro. 667873 3 abarth 2012-07-12 09:40:33 -0700 > I'm afraid I don't have anything ready to be uploaded yet, but I mean any layout tests that work with WebKit API features that are guarded by the ANDROID macro. Typically, LayoutTests don't work with the WebKit API, they work with the web platform API. Also, we generally don't guard things in the Chromium WebKit API with OS-specific macros. I'm happy to look in the chromium-android branch if there are examples there that aren't ready to be uploaded yet. I should be clear that I'm not opposed to this idea. I'm just seeking to understand the motivation. 693562 4 leandrogracia 2012-08-13 05:24:54 -0700 It seems that this was not required after all. Instead of layout tests WebKit unit tests have been used for the case I was considering (bug 93111).