Add ImportHistory class and RecordStorage class.

chrome/browser/chromeos/file_manager/file_manager_jstest.cc

Index: chrome/browser/chromeos/file_manager/file_manager_jstest.cc
diff --git a/chrome/browser/chromeos/file_manager/file_manager_jstest.cc b/chrome/browser/chromeos/file_manager/file_manager_jstest.cc
index db92a316391f7c91600a7b55917888c6c3142d1f..b0b970615ad9075cbd31982b3afdd0823b14b98c 100644
--- a/chrome/browser/chromeos/file_manager/file_manager_jstest.cc
+++ b/chrome/browser/chromeos/file_manager/file_manager_jstest.cc
@@ -60,3 +60,8 @@ IN_PROC_BROWSER_TEST_F(FileManagerJsTest, FileOperationManagerTest) {
   RunTest(base::FilePath(
       FILE_PATH_LITERAL("file_operation_manager_unittest.html")));
 }
+
+IN_PROC_BROWSER_TEST_F(FileManagerJsTest, ImportHistoryTest) {

[mtomasz, 2014/10/27 00:40:11]

Please add TEST=browser_test: *ImportHistoryTest* or sth like that to the CL
description.

[Steve McKay, 2014/10/27 21:06:28]

Done.

Q: What's the background on that? Does it serve a functional role, or just
informative?

[mtomasz, 2014/10/28 01:36:32]

Good question. I was asked by testers to write a way to verify each CL. If it's
automatically tested, then they would like to know about it. But I'm not really
sure if it's a hard rule.

[Steve McKay, 2014/10/28 18:04:01]

I don't mind. Just wondering.

+  RunTest(base::FilePath(
+      FILE_PATH_LITERAL("import_history_unittest.html")));
+}