From a9f1489fd0dc32901823fbe09fc323479a444048 Mon Sep 17 00:00:00 2001 From: Xavier Morel Date: Mon, 29 Oct 2012 13:00:04 +0100 Subject: [PATCH] [FIX] typos bzr revid: xmo@openerp.com-20121029120004-d8tv0hks9d6684az --- addons/web/doc/testing.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/addons/web/doc/testing.rst b/addons/web/doc/testing.rst index 4760f0780eb..2d5876776a3 100644 --- a/addons/web/doc/testing.rst +++ b/addons/web/doc/testing.rst @@ -199,7 +199,7 @@ testing them. Thus, test cases get a DOM scratchpad as its second positional parameter, in a jQuery instance. That scratchpad is fully cleaned up before each test, and as long as it doesn't do anything outside the -scrartchpad your code can do whatever it wants:: +scratchpad your code can do whatever it wants:: // test/demo.js test('DOM content', function (instance, $scratchpad) { @@ -334,7 +334,7 @@ setting up the test case, provide what the RPC responses "should" be, and only test the code between the "user" (the test itself) and the RPC call, before the call is effectively done. -To do this, set the :js:attr:`rpc option <~TestOptions.rpc>` to +To do this, set the :js:attr:`rpc option ` to ``mock``. This will add a third parameter to the test case callback: .. js:function:: mock(rpc_spec, handler) @@ -349,8 +349,8 @@ To do this, set the :js:attr:`rpc option <~TestOptions.rpc>` to In that case, ``handler`` should be a function taking two arguments ``args`` and ``kwargs``, matching the corresponding - arguments on the server side. Hander should simply return the - value as if it were returned by the Python XMLRPC handler:: + arguments on the server side and should simply return the value + as if it were returned by the Python XMLRPC handler:: test('XML-RPC', {rpc: 'mock', asserts: 3}, function (instance, $s, mock) { // set up mocking