Get chrome:// dev tool urls hooked up in content_shell.

content/test/content_test_suite.cc

Index: content/test/content_test_suite.cc
===================================================================
--- content/test/content_test_suite.cc	(revision 132480)
+++ content/test/content_test_suite.cc	(working copy)
@@ -10,6 +10,7 @@
 #include "content/browser/notification_service_impl.h"
 #include "content/public/common/content_client.h"
 #include "content/public/common/content_paths.h"
+#include "content/public/common/url_constants.h"
 #include "content/test/test_content_client.h"
 #include "testing/gtest/include/gtest/gtest.h"
 #include "ui/base/ui_base_paths.h"
@@ -71,6 +72,9 @@
 
   base::TestSuite::Initialize();
 
+  const bool kDontLockStandardSchemes = false;
+  content::RegisterContentSchemes(kDontLockStandardSchemes);

[michaeln, 2012/04/17 04:08:26]

This test suite gets initialized prior SetContentClient having been called. I
could modify it to set a client prior to the register call as
ChromeTestSuite::Initialize() does. That's necessary in the chrome case because
it actually adds custom schemes. In this initializer, no custom schemes get
added.

[jam, 2012/04/17 04:49:51]

yeah i think it's better to add a few more lines to the test suite code, instead
of starting to null check in the content code which we've managed to avoid so
far. i'm just worried about people starting to null check it and writing code to
handle a case that won't happen

[michaeln, 2012/04/17 19:23:32]

Done.

+
   content::RegisterPathProvider();
   ui::RegisterPathProvider();