From 4f4005896c56f09382a69861e69e6c9f191c2592 Mon Sep 17 00:00:00 2001 From: Christophe Monniez Date: Tue, 2 Feb 2021 10:20:06 +0100 Subject: [PATCH] [FIX] runbot: browse a valid record id in test_warning Since odoo/odoo@824a651 the test_warning_from_runbot_abstract was failing for a good reason, the `browse` parameter was a recordset instead of an id. --- runbot/tests/test_runbot.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/runbot/tests/test_runbot.py b/runbot/tests/test_runbot.py index 413c3014..2ce3cce2 100644 --- a/runbot/tests/test_runbot.py +++ b/runbot/tests/test_runbot.py @@ -9,6 +9,6 @@ _logger = logging.getLogger(__name__) class TestRunbot(RunbotCase): def test_warning_from_runbot_abstract(self): - warning_id = self.env['runbot.runbot'].warning('Test warning message') + warning = self.env['runbot.runbot'].warning('Test warning message') - self.assertTrue(self.env['runbot.warning'].browse(warning_id).exists()) + self.assertTrue(self.env['runbot.warning'].browse(warning.id).exists())