Cast: Isolate for tab capture end2end test

chrome/tab_capture_end2end_tests.isolate

Index: chrome/tab_capture_end2end_tests.isolate
diff --git a/chrome/tab_capture_end2end_tests.isolate b/chrome/tab_capture_end2end_tests.isolate
new file mode 100644
index 0000000000000000000000000000000000000000..1a3e9fe4f6c79e8d1ff0b30968a65a9d7ecf8c93
--- /dev/null
+++ b/chrome/tab_capture_end2end_tests.isolate
@@ -0,0 +1,25 @@
+# Copyright 2014 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.
+{
+  'includes': [
+    'browser_tests.isolate',
+  ],
+  'conditions': [
+    ['OS=="linux" or OS=="mac" or OS=="win"', {
+      'variables': {
+        'command': [
+          '../testing/test_env.py',
+          '<(PRODUCT_DIR)/browser_tests<(EXECUTABLE_SUFFIX)',
+          '--test-launcher-bot-mode',
+          '--enable-gpu',
+          '--test-launcher-jobs=1',
+          '--gtest_filter=TabCaptureApiPixelTest.EndToEnd*',

[Paweł Hajdan Jr., 2014/05/19 10:23:23]

I don't recommend using gtest_filter in this way. Depending on what you're
trying to do, there should be a better way.

Main part of the rationale is that it becomes *significantly* harder to ensure
separate configs (like CQ and main waterfall) are in sync when gtest_filter is
present.

[Ken Russell (switch to Gerrit), 2014/05/19 17:47:21]

The intent is to run a small subset of the browser_tests. Can you suggest
another way?

Note I specifically do not want to put the gtest_filter in the GPU recipe. We've
run into multiple problems trying to make changes to tests' configurations when
some of the configuration is in the recipe and the rest is in the Chromium
workspace. The configuration of these tests should be entirely in the Chromium
workspace and thus in the isolate.

+        ],
+        'isolate_dependency_untracked': [
+          'test/data/extensions/api_test/tab_capture/',
+        ],
+      },
+    }],
+  ],
+}