From ea9df2af195b5b08909dc30e05bab95f6cfcd66f Mon Sep 17 00:00:00 2001 From: rockot Date: Thu, 22 Jan 2015 12:26:36 -0800 Subject: s/app_shell_browsertests/extensions_browsertests/g We would like to use app_shell as the basis for all content-browser integration tests within the extensions layer. This simply moves the test target up to the parent //extensions path and renames it to extensions_browsertests BUG=388893 R=yoz@chromium.org Review URL: https://codereview.chromium.org/797023006 Cr-Commit-Position: refs/heads/master@{#312669} --- extensions/shell/test/shell_test.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'extensions/shell/test') diff --git a/extensions/shell/test/shell_test.cc b/extensions/shell/test/shell_test.cc index e18ffcf..183303a 100644 --- a/extensions/shell/test/shell_test.cc +++ b/extensions/shell/test/shell_test.cc @@ -21,7 +21,7 @@ AppShellTest::AppShellTest() : browser_context_(NULL), extension_system_(NULL) { #if defined(OS_MACOSX) // TODO(phajdan.jr): Make browser tests self-contained on Mac; remove this. // Set up the application path as though we we are inside the App Shell.app - // bundle, rather than the top-level app_shell_browsertests, because we + // bundle, rather than the top-level extensions_browsertests, because we // make many assumptions about where the executable is located. base::FilePath app_shell_path; CHECK(PathService::Get(base::FILE_EXE, &app_shell_path)); -- cgit v1.1