[FIX] pos_restaurant: remove ambiguity to prevent runbot error

This random runbot error happens when the tour manager is steps ahead of
the rendering:
1. clicks Second Floor button
2. checks T1 - this won't fail even if the Second Floor hasn't finished
rendering because Main Floor has tables that start with `T1`.
3. clicks a table in Main Floor with T1 in name
4. Then error because the back to floor button should be Second Floor.

Tables that start with `T1` is created in Main Floor during the tour,
however, we also have one in Second Floor. To make sure that the runbot
correctly waits and clicks for the right table, we use T3 in Second
Floor instead of it's T1.

closes odoo/odoo#59168

X-original-commit: 8e65a220cadefe41df9fcc2172d60ff90ea5b584
Signed-off-by: Christophe Monniez (moc) <moc@odoo.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/addons/pos_restaurant/static/tests/tours/FloorScreen.tour.js b/addons/pos_restaurant/static/tests/tours/FloorScreen.tour.js
index af52936264c..6c542e66858 100644
--- a/addons/pos_restaurant/static/tests/tours/FloorScreen.tour.js
+++ b/addons/pos_restaurant/static/tests/tours/FloorScreen.tour.js
@@ -101,9 +101,9 @@ odoo.define('pos_restaurant.tour.FloorScreen', function (require) {
 
     // Opening product screen in second floor should go back to second floor
     FloorScreen.do.clickFloor('Second Floor');
-    FloorScreen.check.hasTable('T1');
-    FloorScreen.do.clickTable('T1');
-    Chrome.check.backToFloorTextIs('Second Floor', 'T1');
+    FloorScreen.check.hasTable('T3');
+    FloorScreen.do.clickTable('T3');
+    Chrome.check.backToFloorTextIs('Second Floor', 'T3');
 
     Tour.register('FloorScreenTour', { test: true, url: '/pos/ui' }, getSteps());
 });