Input latency performance test that uses tracing.

chrome/test/perf/browser_perf_test.h

Index: chrome/test/perf/browser_perf_test.h
diff --git a/chrome/test/perf/browser_perf_test.h b/chrome/test/perf/browser_perf_test.h
new file mode 100644
index 0000000000000000000000000000000000000000..80eb39218f8af12ab2ec7b0a395e47a2933df136
--- /dev/null
+++ b/chrome/test/perf/browser_perf_test.h
@@ -0,0 +1,29 @@
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_TEST_PERF_BROWSER_PERF_TEST_H_
+#define CHROME_TEST_PERF_BROWSER_PERF_TEST_H_
+#pragma once
+
+#include "chrome/test/base/in_process_browser_test.h"
+
+class CommandLine;
+
+class BrowserPerfTest : public InProcessBrowserTest {
+ public:
+  BrowserPerfTest();
+  virtual ~BrowserPerfTest();
+
+  // Set up common browser perf test flags. Typically call down to this if
+  // overridden.
+  virtual void SetUpCommandLine(CommandLine* command_line) OVERRIDE;
+
+  // Prints IO performance data for use by perf graphs.
+  void PrintIOPerfInfo(const char* test_name);

[Paweł Hajdan Jr., 2011/12/22 08:08:39]

nit: I'm not a fan of "const char*" in the public interface... Could you convert
that to const std::string& ?

My rationale is that there is an implicit conversion from char* to std::string,
and obviously std::string can be passed as std::string, but if you have a
std::string, you have to explicitly use .c_str() when the argument type is
char*, and I don't see anything we'd be gaining by that.

[jbates, 2011/12/22 19:39:34]

Done.

+
+  // Prints memory usage data for use by perf graphs.
+  void PrintMemoryUsageInfo(const char* test_name);
+};
+
+#endif  // CHROME_TEST_PERF_BROWSER_PERF_TEST_H_