Bug 1316622 - Move Marionette harness tests to new timeouts API; r=whimboo a=test-only
authorAndreas Tolfsen <ato@mozilla.com>
Thu, 10 Nov 2016 21:04:20 +0000
changeset 352629 84c312a3b3bfa5f77177b6421b5942efd48cff20
parent 352628 c5fb9074db086843d3ddc21b93866b239f58c680
child 352630 3b7d7efc65023b83443bf14abfd25ac5a78258df
push id6795
push userjlund@mozilla.com
push dateMon, 23 Jan 2017 14:19:46 +0000
treeherdermozilla-esr52@76101b503191 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerswhimboo, test-only
bugs1316622
milestone52.0a2
Bug 1316622 - Move Marionette harness tests to new timeouts API; r=whimboo a=test-only MozReview-Commit-ID: LXjifQ11xI4
testing/marionette/harness/docs/basics.rst
--- a/testing/marionette/harness/docs/basics.rst
+++ b/testing/marionette/harness/docs/basics.rst
@@ -174,10 +174,10 @@ The async method works the same way, exc
        setTimeout(function() {
          marionetteScriptFinished("all done");
        }, arguments[0]);
    """, script_args=[1000])
    assert result == "all done"
 
 Beware that running asynchronous scripts can potentially hang the program
 indefinitely if they are not written properly. It is generally a good idea to
-set a script timeout using :func:`~Marionette.set_script_timeout` and handling
+set a script timeout using :func:`~Marionette.timeout.script` and handling
 `ScriptTimeoutException`.