Simplify directory path accounting.

webkit/fileapi/file_system_file_util_unittest.cc

Index: webkit/fileapi/file_system_file_util_unittest.cc
diff --git a/webkit/fileapi/file_system_file_util_unittest.cc b/webkit/fileapi/file_system_file_util_unittest.cc
index afa742bfb9305a82f86cd3a02f074d0adc360b9f..459a19c489e6e7f4e31e49eee1b917cb1e3c75d1 100644
--- a/webkit/fileapi/file_system_file_util_unittest.cc
+++ b/webkit/fileapi/file_system_file_util_unittest.cc
@@ -64,6 +64,10 @@ class FileSystemFileUtilTest : public testing::Test {
 
   FileSystemOperationContext* NewContext(FileSystemTestOriginHelper* helper) {
     FileSystemOperationContext* context = helper->NewOperationContext();
+    // We need to allocate quota for paths for
+    // TestCrossFileSystemCopyMoveHelper, since it calls into OFSFU, which
+    // charges quota for paths.

[Dai Mikurube (NOT FULLTIME), 2011/08/16 05:11:00]

Does this test require OFSFU?  Or could it be in OFSFUTest?

[ericu, 2011/08/16 21:16:31]

The cross-filesystem copy/move is a FSFU method.  It happens to call into OFSFU
in this case.  We could theoretically test it by copying from one LocalFSFU to
another, but given that they'd both really be looking at the same underlying OS
filesystem, I don't think we could trust the test quite as much.  There could be
bugs that would slip through.

+    context->set_allowed_bytes_growth(1024 * 1024);
     return context;
   }
 
@@ -117,6 +121,7 @@ class FileSystemFileUtilTest : public testing::Test {
     copy_context->set_dest_origin_url(dest_helper.origin());
     copy_context->set_src_type(src_helper.type());
     copy_context->set_dest_type(dest_helper.type());
+    copy_context->set_allowed_bytes_growth(1024 * 1024); // OFSFU path quota.
 
     if (copy)
       ASSERT_EQ(base::PLATFORM_FILE_OK,