Test NaCl version of ppapi_tests via ui_tests

ppapi/tests/test_url_loader.cc

Index: ppapi/tests/test_url_loader.cc
===================================================================
--- ppapi/tests/test_url_loader.cc	(revision 110336)
+++ ppapi/tests/test_url_loader.cc	(working copy)
@@ -87,8 +87,11 @@
   RUN_TEST_FORCEASYNC_AND_NOT(BinaryDataPOST, filter);
   RUN_TEST_FORCEASYNC_AND_NOT(CustomRequestHeader, filter);
   RUN_TEST_FORCEASYNC_AND_NOT(FailsBogusContentLength, filter);
-  RUN_TEST_FORCEASYNC_AND_NOT(SameOriginRestriction, filter);
-  RUN_TEST_FORCEASYNC_AND_NOT(CrossOriginRequest, filter);
+  // Disable portion of test which failes when the HTTP server's

[dmichael (off chromium), 2011/11/18 20:10:25]

nit: failes->fails

[noelallen1, 2011/11/18 20:39:39]

Done.

+  // data_dir is moved to PRODUCT_DIR.
+  // http://code.google.com/p/chromium/issues/detail?id=103690
+  //  RUN_TEST_FORCEASYNC_AND_NOT(SameOriginRestriction, filter);
+  //  RUN_TEST_FORCEASYNC_AND_NOT(CrossOriginRequest, filter);

[dmichael (off chromium), 2011/11/18 20:10:25]

You should be able to disable these only for NaCl, right?

[noelallen1, 2011/11/18 20:39:39]

They fail for both trusted and untrusted tests when you move the server.   I
felt it was better to always move the server, than conditionally move the server
and have different behavior.

   RUN_TEST_FORCEASYNC_AND_NOT(JavascriptURLRestriction, filter);
   RUN_TEST_FORCEASYNC_AND_NOT(MethodRestriction, filter);
   RUN_TEST_FORCEASYNC_AND_NOT(HeaderRestriction, filter);