Use ExecuteJavascriptInWebFrameNotifyResult to return results even in error condition

chrome/browser/ui/webui/web_ui_browsertest.cc

Index: chrome/browser/ui/webui/web_ui_browsertest.cc
diff --git a/chrome/browser/ui/webui/web_ui_browsertest.cc b/chrome/browser/ui/webui/web_ui_browsertest.cc
index 3817612619a61c8a7daf4884bbc5cab12a9f0e53..e5efc400ad467087f060443a7e105a392b15375a 100644
--- a/chrome/browser/ui/webui/web_ui_browsertest.cc
+++ b/chrome/browser/ui/webui/web_ui_browsertest.cc
@@ -201,6 +201,14 @@ IN_PROC_BROWSER_TEST_F(WebUIBrowserTest, TestSamplePass) {
   ui_test_utils::NavigateToURL(browser(), GURL(chrome::kChromeUIDownloadsURL));
 
   ASSERT_TRUE(RunJavascriptTest("testAssertFalse"));
+  ASSERT_FALSE(RunJavascriptTest("FAILS_testAssertFalse"));
   ASSERT_TRUE(RunJavascriptTest("testInitialFocus"));
   ASSERT_FALSE(RunJavascriptTest("testConsoleError"));
 }
+
+// This fails on purpose to test hanging case in crbug.com/85990

[Paweł Hajdan Jr., 2011/06/15 08:18:21]

If this starts passing you won't get any notification. FAILS does not mean
XFAIL. Also, how long does this test take to run?

[Sheridan Rawlins, 2011/06/15 15:41:14]

It was previously the 25s timeout, but with these changes it is now immediate!

Does gtest have a notion of XFAIL?  I don't think so - I'll update the test to
pass by doing checks instead of gtest ASSERT* here.

On 2011/06/15 08:18:21, Paweł Hajdan Jr. wrote:

[Paweł Hajdan Jr., 2011/06/15 15:49:30]

Cool!
Right, I don't think it has XFAIL. FAILS has been added for Chromium in our test
suite, but it only works one way: when a test marked as FAILS fails, the failure
does not influence the exit code; however, if such a test passes, the exit code
is also not changed.

+IN_PROC_BROWSER_TEST_F(WebUIBrowserTest, FAILS_TestFailsFast) {
+  AddLibrary(FilePath(FILE_PATH_LITERAL("sample_downloads.js")));
+  ui_test_utils::NavigateToURL(browser(), GURL(chrome::kChromeUIDownloadsURL));
+  ASSERT_FALSE(RunJavascriptTest("FAILS_BogusFunctionName"));
+}