Bug 1267481 - Increase test_session_form_data.html timeout. r=gbrown, a=test-only
authorJan Henning <jh+bugzilla@buttercookie.de>
Sat, 30 Apr 2016 18:44:50 +0200
changeset 333225 1dd7b155900eb230dcbbf6e08441f565e60686f6
parent 333224 997a8557995d1aa1a0b0e1c6375c5eb374615004
child 333226 53d94e77fd504839e52e67318f01c802ff3d7cf2
push id6048
push userkmoir@mozilla.com
push dateMon, 06 Jun 2016 19:02:08 +0000
treeherdermozilla-beta@46d72a56c57d [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersgbrown, test-only
bugs1267481
milestone48.0a2
Bug 1267481 - Increase test_session_form_data.html timeout. r=gbrown, a=test-only Opening/navigating within/restoring a tab seems to be relatively slow on the emulator and as we want to test whether form data is preserved by the session store after closing and restoring a tab, quite a bit of time is accumulated that way. MozReview-Commit-ID: 3LhLuZIZ2z7
mobile/android/tests/browser/chrome/test_session_form_data.html
--- a/mobile/android/tests/browser/chrome/test_session_form_data.html
+++ b/mobile/android/tests/browser/chrome/test_session_form_data.html
@@ -21,16 +21,19 @@ const { classes: Cc, interfaces: Ci, uti
 
 Cu.import("resource://gre/modules/XPCOMUtils.jsm");
 Cu.import("resource://gre/modules/Services.jsm");
 Cu.import("resource://gre/modules/Task.jsm");
 
 let gChromeWin;
 let gBrowserApp;
 
+// Waiting for a tab to load or restore can be slow on the emulator.
+SimpleTest.requestLongerTimeout(2);
+
 setup_browser();
 
 function queryElement(contentWindow, data) {
   let frame = contentWindow;
   if (data.hasOwnProperty("frame")) {
     frame = contentWindow.frames[data.frame];
   }