summaryrefslogtreecommitdiffstats
path: root/ppapi/tests/testing_instance.h
diff options
context:
space:
mode:
authorbauerb@chromium.org <bauerb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-09-04 10:28:00 +0000
committerbauerb@chromium.org <bauerb@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-09-04 10:28:00 +0000
commitbf033f9c17ce44ad5bd8ab0df67fdf70b922b5e1 (patch)
tree602a8215c38456468cbc539359966de800ab0bd0 /ppapi/tests/testing_instance.h
parenta228c84d5b1e0aa975b5e7732dfdbe9bcb78b028 (diff)
downloadchromium_src-bf033f9c17ce44ad5bd8ab0df67fdf70b922b5e1.zip
chromium_src-bf033f9c17ce44ad5bd8ab0df67fdf70b922b5e1.tar.gz
chromium_src-bf033f9c17ce44ad5bd8ab0df67fdf70b922b5e1.tar.bz2
Add infobar for PPAPI broker usage.
BUG=142639 Review URL: https://chromiumcodereview.appspot.com/10826164 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154742 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/tests/testing_instance.h')
-rw-r--r--ppapi/tests/testing_instance.h11
1 files changed, 6 insertions, 5 deletions
diff --git a/ppapi/tests/testing_instance.h b/ppapi/tests/testing_instance.h
index 33ed21c..013c694 100644
--- a/ppapi/tests/testing_instance.h
+++ b/ppapi/tests/testing_instance.h
@@ -25,11 +25,12 @@ class TestCase;
// How signaling works:
//
// We want to signal to the Chrome browser test harness
-// (chrome/test/ui/ppapi_uitest.cc) that we're making progress and when we're
-// done. This is done using the DOM controlller. The browser test waits for a
-// message from it. We don't want to have a big wait for all tests in a TestCase
-// since they can take a while and it might timeout. So we send it pings
-// between each test to tell it that we're still running tests and aren't stuck.
+// (chrome/test/ppapi/ppapi_browsertest.cc) that we're making progress and when
+// we're done. This is done using the DOM controlller. The browser test waits
+// for a message from it. We don't want to have a big wait for all tests in a
+// TestCase since they can take a while and it might timeout. So we send it
+// pings between each test to tell it that we're still running tests and aren't
+// stuck.
//
// If the value of the message is "..." then that tells the test runner that
// the test is progressing. It then waits for the next message until it either