Tuesday, December 20, 2016
1 change · master
Code cleanup and technical improvements
A standard demo portal user is now available from the core base setup instead of depending on the portal app. This makes it easier for teams to test portal-related website features consistently, even when the portal app itself is not installed.
Original PR description
Description of the issue/feature this PR addresses: Allows to write tests (and, more specifically, tours) with portal permissions when `portal` module is not installed. Current behavior before PR: If you wanted to create a tour for any `website_portal` submodule, you could have no `portal` module installed, so you cannot rely in using Demo Portal User as the tour's login. This is because we now have 2 portal suites: `portal` and `website_portal`, both independent, but the Demo Portal User is only created in the former one. Desired behavior after PR is merged: Now we have a Demo Portal User in the base addon, so any addon that implements any behavior based on the Portal group can write tests & tours using Demo Portal User as the login. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @Tecnativa