Index: chrome/browser/extensions/extension_tabs_apitest.cc |
diff --git a/chrome/browser/extensions/extension_tabs_apitest.cc b/chrome/browser/extensions/extension_tabs_apitest.cc |
index 672f6a75bcd2ca4e110eff9513da7eaaed213304..68f465ce35c81b80c7d23e080ebf2b61eb432732 100644 |
--- a/chrome/browser/extensions/extension_tabs_apitest.cc |
+++ b/chrome/browser/extensions/extension_tabs_apitest.cc |
@@ -222,3 +222,8 @@ IN_PROC_BROWSER_TEST_F(ExtensionApiTest, MAYBE_GetViewsOfCreatedWindow) { |
ASSERT_TRUE(RunExtensionSubtest("tabs/basics", "get_views_window.html")) |
<< message_; |
} |
+ |
+// Adding a new test? Awesome. But API tests are the old hotness. The |
+// new hotness is extension_test_utils. See extension_tabs_test.cc for |
+// an example. We are trying to phase out many uses of API tests as |
+// they tend to be flakey. |
pastarmovj
2011/10/27 09:14:31
Isn't it flaky instead of flakey? :)
rustema
2011/10/29 06:43:21
Yeah, that may be confusing. Changed.
|