Files
odoo_source/addons/website/static/tests/tours/restricted_editor.js
T
qsm-odoo accb4b3245 [IMP] website, *: review website tour utils
*: test_website, website_blog, website_crm, website_event,
   website_forum, website_hr_recruitment, website_mass_mailing,
   website_sale, website_sale_wishlist, website_slides

- Make sure that all website tours reaching the website preview before
  their first step use the related website util to register their tour.

- Rename the website util to register a tour starting on the website
  preview from `registerEditionTour` to `registerWebsitePreviewTour`.
  Having a method using "Edition" in its name and having a boolean
  parameter named `edition` was a bit... strange.

- For both non edit mode and edit mode as a first step, ensure the util
  sets a high timeout for the first step. Indeed loading both the
  backend and the frontend (in the iframe) and potentially starting the
  edit mode can take a long time in automatic tests. We'll try and
  decrease the need for this high timeout of course.

- Review the implementation of those utils to be more consistent and
  also fix one or two mistakes in them.

closes odoo/odoo#100024

Related: odoo/design-themes#588
Signed-off-by: Quentin Smetz (qsm) <qsm@odoo.com>
2022-09-12 17:33:39 +02:00

17 lines
450 B
JavaScript

odoo.define("website.tour.restricted_editor", function (require) {
"use strict";
var wTourUtils = require("website.tour_utils");
wTourUtils.registerWebsitePreviewTour("restricted_editor", {
test: true,
url: "/",
}, [{
trigger: '.o_edit_website_container a',
content: "Click \"EDIT\" button of website as Restricted Editor",
}, {
trigger: '#oe_snippets.o_loaded',
content: "Check that the snippets loaded properly",
}]);
});