odoo/odoo#196095
Created by fw-bot
Merged
at 2fc0c648b298fe0e2eba1c77f5344e5bf7ff07e5
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:saas-18.1-18.0-testing_synchronisation-moda-nF01-fw
- head
- 1bf0374538e8510eb7100750dd853d1e928c7f83
- merged
- 9 months ago by POS IoT, David Monnom (moda)
| odoo/odoo | |
|---|---|
| 18.0 | #195344 |
| saas-18.1 | #196095 |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #196327 |
[FW][IMP] point_of_sale, pos_restaurant: tour for testing synchronisation
Before we had no solution to test the synchronisation of the pos. In classic tours websocket are not supported. And we cannot launch two tours in parallel.
This commit add the possibility to load test assets in the PoS during our development. That's allow us to launch tour in loop in two different browser and test the synchronisation by creating orders, payment etc.
Tour assets are only added by adding &tours=True in the URL of the PoS interface.
Forward-Port-Of: #195344