| 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..89362319135b7d099eadf87779f3a784da19b408 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 flaky.
|
|
|