Prettify output from chrome.fileSystem.getDisplayPath for POSIX profile directories

chrome/browser/extensions/api/file_system/file_system_apitest.cc

Index: chrome/browser/extensions/api/file_system/file_system_apitest.cc
diff --git a/chrome/browser/extensions/api/file_system/file_system_apitest.cc b/chrome/browser/extensions/api/file_system/file_system_apitest.cc
index 5ef2a7f28844d31c2865e37f953bf5af0e8f8fe4..a4c3350f0eefe1e916ff257602332288e1b4fdd2 100644
--- a/chrome/browser/extensions/api/file_system/file_system_apitest.cc
+++ b/chrome/browser/extensions/api/file_system/file_system_apitest.cc
@@ -48,9 +48,13 @@ IN_PROC_BROWSER_TEST_F(FileSystemApiTest, FileSystemApiGetDisplayPath) {
       << message_;
 }
 
-#if defined(OS_WIN)
 IN_PROC_BROWSER_TEST_F(FileSystemApiTest, FileSystemApiGetDisplayPathPrettify) {
-  ASSERT_TRUE(PathService::OverrideAndCreateIfNeeded(base::DIR_PROFILE,
+#if defined(OS_WIN)
+  int override = base::DIR_PROFILE;
+#elif defined(OS_POSIX)
+  int override = base::DIR_HOME;
+#endif

[benwells, 2012/07/10 23:57:49]

Again, I don't like relying on OS_POSIX == !OS_WIN

[thorogood, 2012/07/11 00:30:24]

I've guarded this test by a define again.

+  ASSERT_TRUE(PathService::OverrideAndCreateIfNeeded(override,
       test_root_folder_, false));
 
   FilePath test_file = test_root_folder_.AppendASCII("gold.txt");
@@ -59,7 +63,6 @@ IN_PROC_BROWSER_TEST_F(FileSystemApiTest, FileSystemApiGetDisplayPathPrettify) {
   ASSERT_TRUE(RunPlatformAppTest(
       "api_test/file_system/get_display_path_prettify")) << message_;

[Mihai Parparita -not on Chrome, 2012/07/11 00:21:10]

Sorry for not catching this in the other review, but for tests like this one
where you're just checking the result of an ExtensionFunction invocation, it's
less overhead* to do it directly in C++.  There's a bunch of helpers in the
extension_function_test_utils namespace, see
http://code.google.com/p/chromium/source/search?q=%3A%3ARunFunction+file%3Atest
for sample uses.

* both in that the tests will run faster, and in that you don't have to create a
new app/extension manifest, background page, etc. for the test.

[thorogood, 2012/07/11 04:07:45]

Thanks for the insight! I've had a play with it, but I'm not sure if this is the
right approach here. The getDisplayPath function only makes sense on an
initialized FileEntry, which we only get from calling another API function which
builds it and registers an isolated filesystem, so I feel like it's still neater
to test via a manifest.

Some of the other tests here that don't depend on other API calls for their
results might be better candidates.

[Mihai Parparita -not on Chrome, 2012/07/11 05:32:28]

Fair enough.

 }
-#endif
 
 IN_PROC_BROWSER_TEST_F(FileSystemApiTest, FileSystemApiOpenExistingFileTest) {
   FilePath test_file = TempFilePath("open_existing.txt", true);