From da37acedf62940c5f074822f10e52520e10a43cf Mon Sep 17 00:00:00 2001
From: Xavier Morel <xmo@openerp.com>
Date: Fri, 27 Apr 2012 10:11:14 +0200
Subject: [PATCH] [TESTS] m2o completion with no match on name_search

bzr revid: xmo@openerp.com-20120427081114-8tn0x6xaky2ivqwm
---
 addons/web/static/test/search.js | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/addons/web/static/test/search.js b/addons/web/static/test/search.js
index 276ff3d21b2..ec93f1a6707 100644
--- a/addons/web/static/test/search.js
+++ b/addons/web/static/test/search.js
@@ -623,6 +623,24 @@ $(document).ready(function () {
                 deepEqual(f2.values.toJSON(), [{label: 'choice @', value: 43}]);
             });
     });
+    asyncTest("M2O no match", 5, function () {
+        instance.connection.responses['/web/dataset/call_kw'] = function (req) {
+            equal(req.params.method, "name_search");
+            equal(req.params.model, "dummy.model");
+            deepEqual(req.params.args, []);
+            deepEqual(req.params.kwargs.name, 'bob');
+            return {result: []}
+        };
+        var view = {inputs: []};
+        var f = new instance.web.search.ManyToOneField(
+            {attrs: {string: 'Dummy'}}, {relation: 'dummy.model'}, view);
+        f.complete("bob")
+            .always(start)
+            .fail(function (error) { ok(false, error.message); })
+            .done(function (c) {
+                ok(!c, "no match should yield no completion");
+            });
+    });
 
     // TODO: test drawer rendering
     // TODO: UI tests?