From 80c2204e20beda01afc48d8f5dcb599a6abdb7a3 Mon Sep 17 00:00:00 2001 From: Christophe Monniez Date: Wed, 1 Jun 2022 11:47:52 +0000 Subject: [PATCH] [FIX] tests: increase navigation timeout When instrumenting the Chrome Browser and asking to navigate to a location, it happens that the 10 seconds timeout is exceeded. This happens particularly when executing qunit tests by navigating to `/web/tests`. This route has an average loading time around 7 seconds but when the runbot is loaded, it can exceed 10 seconds. With this commit, the timeout is set to 15s. It would be better to split the qunit tests by module in order to avoid the huge assets bundle generation. closes odoo/odoo#92699 X-original-commit: 6c0fa6b72bf5d15e8323b81cf930a01d4c0f3291 Signed-off-by: Christophe Monniez (moc) --- odoo/tests/common.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/odoo/tests/common.py b/odoo/tests/common.py index b9552b50ca8..880d1b365cd 100644 --- a/odoo/tests/common.py +++ b/odoo/tests/common.py @@ -1355,7 +1355,7 @@ class ChromeBrowser: def navigate_to(self, url, wait_stop=False): self._logger.info('Navigating to: "%s"', url) - nav_result = self._websocket_request('Page.navigate', params={'url': url}) + nav_result = self._websocket_request('Page.navigate', params={'url': url}, timeout=15.0) self._logger.info("Navigation result: %s", nav_result) if wait_stop: frame_id = nav_result['frameId']