Have media content and chrome browser tests load data from media/test/data

content/browser/media/media_source_browsertest.cc

Index: content/browser/media/media_source_browsertest.cc
diff --git a/content/browser/media/media_source_browsertest.cc b/content/browser/media/media_source_browsertest.cc
index d5d86154637056c7242f684dbd2087d8372ac66d..7a6bcc963fd57d84cab101ed619107b94c888182 100644
--- a/content/browser/media/media_source_browsertest.cc
+++ b/content/browser/media/media_source_browsertest.cc
@@ -40,8 +40,8 @@ class MediaSourceTest : public content::MediaBrowserTest {
     }
 
     std::vector<StringPair> query_params;
-    query_params.push_back(std::make_pair("mediafile", media_file));
-    query_params.push_back(std::make_pair("mediatype", media_type));
+    query_params.push_back(std::make_pair("mediaFile", media_file));

[jrummell, 2014/07/02 00:33:40]

Should these tags (mediaFile, mediaType, keySystem, useMSE, etc.) be defined in
one place like test_utils?

[shadi, 2014/07/02 19:23:36]

It seems like an over kill. These params are tied to whatever HTML and JS code
uses, so either side can break things....

+    query_params.push_back(std::make_pair("mediaType", media_type));

[jrummell, 2014/07/02 00:33:40]

The other place where parameters are created has useMSE flag. Since this
requires MSE (at least from the comment above), should we not specify it as a
parameter instead of relying on a default?

[shadi, 2014/07/02 19:23:36]

True, but this test only uses media_source_player.html which explicitly loads
video by MSE commands.

     RunMediaTestPage("media_source_player.html", &query_params, expectation,
                      true);
   }