[chromedriver] Add an error autoreporting feature that automatically raises errors from browser logs

chrome/test/chromedriver/logging.cc

Index: chrome/test/chromedriver/logging.cc
diff --git a/chrome/test/chromedriver/logging.cc b/chrome/test/chromedriver/logging.cc
index 5933f2a8c202cb85786bedfba5fb728b3444017e..2142183bfde9c11bc83d1e70f2f099867564a690 100644
--- a/chrome/test/chromedriver/logging.cc
+++ b/chrome/test/chromedriver/logging.cc
@@ -150,6 +150,26 @@ scoped_ptr<base::ListValue> WebDriverLog::GetAndClearEntries() {
   return ret.Pass();
 }
 
+std::string WebDriverLog::GetFirstErrorMessage() const {

[chrisgao (Use stgao instead), 2014/01/09 22:11:55]

How do you handle error messages resulted from the page of navigation1 while we
are on the page of navigation2?

I found there is one DevTools event "Console.messagesCleared". You may have a
check.

[samuong, 2014/01/16 00:29:28]

In this case the error from navigation1 will get autoreported, even though we're
on the page of navigation2. I think this is the best way to do it as it ensures
that error messages don't get missed.

Chromedriver already prepends a URL to each error message, so this should make
it obvious to users which page an error message belongs to.

+  for (base::ListValue::iterator it = entries_->begin();
+       it != entries_->end();
+       ++it) {
+    base::DictionaryValue* log_entry = NULL;
+    (*it)->GetAsDictionary(&log_entry);
+    if (log_entry != NULL) {
+      std::string level;
+      if (log_entry->GetString("level", &level)) {
+        if (level.compare(kLevelToName[Log::kError]) == 0) {

[chrisgao (Use stgao instead), 2014/01/09 22:11:55]

level == kLevelToName[Log::kError] ?

[samuong, 2014/01/16 00:29:28]

Done. Obviously I'm still working on kicking the Java habit.

+          std::string message;
+          if (log_entry->GetString("message", &message))
+            return message;

[chrisgao (Use stgao instead), 2014/01/09 22:11:55]

If we do not clear the error message from the list and the client side doesn't
pull the log(As we return a UnknownError, the client side couldn't tell the
error from others.), in all following commands, we will always hit the same
error or maybe a newer one.

Any idea to handle it?

[samuong, 2014/01/16 00:29:28]

When an error is auto-reported, I think most clients will either bail or call
GET_LOGS (which will clear any subsequent error messages). But if they don't,
then I agree that it is a bit weird to throw the same error at them over and
over again.

As you suggested, let's address this in a followup CL, so that we can discuss
exactly how chromedriver should behave in this situation.

+        }
+      }
+    }
+  }
+  return "";

[chrisgao (Use stgao instead), 2014/01/09 22:11:55]

"" -> std::string()

[samuong, 2014/01/16 00:29:28]

Done.

+}
+
 void WebDriverLog::AddEntryTimestamped(const base::Time& timestamp,
                                        Log::Level level,
                                        const std::string& source,