Remove details panel.

chrome/browser/chromeos/file_manager/file_manager_browsertest.cc

Index: chrome/browser/chromeos/file_manager/file_manager_browsertest.cc
diff --git a/chrome/browser/chromeos/file_manager/file_manager_browsertest.cc b/chrome/browser/chromeos/file_manager/file_manager_browsertest.cc
index 560bc46d88236a702a47a8b203f0f92a986f9e9e..d9e044d70ea140296c719f9c92b91894043bd669 100644
--- a/chrome/browser/chromeos/file_manager/file_manager_browsertest.cc
+++ b/chrome/browser/chromeos/file_manager/file_manager_browsertest.cc
@@ -54,19 +54,6 @@ IN_PROC_BROWSER_TEST_P(FileManagerBrowserTestWithLegacyEventDispatch, Test) {
   StartTest();
 }
 
-// Test fixture class for details panel.
-// TODO(ryoh): remove after we release details panel feature.
-class FileManagerDetailsPanelBrowserTest : public FileManagerBrowserTest {
-  void SetUpCommandLine(base::CommandLine* command_line) override {
-    FileManagerBrowserTest::SetUpCommandLine(command_line);
-    command_line->AppendSwitch("--enable-files-details-panel");
-  }
-};
-
-IN_PROC_BROWSER_TEST_P(FileManagerDetailsPanelBrowserTest, Test) {
-  StartTest();
-}
-
 // Unlike TEST/TEST_F, which are macros that expand to further macros,
 // INSTANTIATE_TEST_CASE_P is a macro that expands directly to code that
 // stringizes the arguments. As a result, macros passed as parameters (such as
@@ -203,14 +190,6 @@ WRAPPED_INSTANTIATE_TEST_CASE_P(
     FileManagerBrowserTest,
     ::testing::Values(TestParameter(NOT_IN_GUEST_MODE, "openQuickView")));
 
-WRAPPED_INSTANTIATE_TEST_CASE_P(
-    DetailsPanel,
-    FileManagerDetailsPanelBrowserTest,
-    ::testing::Values(
-        TestParameter(NOT_IN_GUEST_MODE, "openDetailsPanel"),
-        TestParameter(NOT_IN_GUEST_MODE, "openDetailsPanelForSingleFile"),
-        TestParameter(NOT_IN_GUEST_MODE, "openSingleFileAndSeeDetailsPanel")));
-
 #if defined(DISABLE_SLOW_FILESAPP_TESTS)
 #define MAYBE_DirectoryTreeContextMenu DISABLED_DirectoryTreeContextMenu
 #else