summaryrefslogtreecommitdiff
path: root/addons/event/tests/test_event_security.py
AgeCommit message (Collapse)Author
2020-08-17[FIX] website_event(_*): improve user flow and experience from frontendstd-odoo
PURPOSE Provide some fixes after internal test deployment of event online features. Notably: user registration flow, various fixes in templates. Also add some unit tests to avoid regressions while working on event features. LINKS Task ID-2169118 odoo/odoo#55967 odoo/enterprise#12438 X-original-commit: e66684b23eebaadc3df7b908427d3d7a83d4f0a0
2020-03-31[REF] (website_)event(_sale): change seats_availability field to seats_limitedPatrick Hoste
PURPOSE Change seats_availability selection field into a boolean field and rename it to seats_limited for consistency. SPECIFICATION Change all the tests accordingly. Task ID : 2198660 PR : #46659
2020-03-17[IMP] event: avoid relying on data in testsqmo-odoo
This commit removed the reference to a particular event.stage and creates it instead. LINKS TaskID: 2170834 PR: #45372
2020-03-10[REF] event : move from onchange / default to stored editable computed fieldsThibault Delavallée
PURPOSE Try to move from onchange / default_get to stored editable computed fields. Behavior should be the same (computed or set by user), with support of create / write / onchange field update without additional code. SPECIFICATIONS: GLOBAL RULES Update classic fields updated in some cases by onchange and/or default methods by fields with store=True, readonly=False. It means their value comes either from manual user input, either from trigger based computation. Remove onchange and default_get when possible, leading to an unique computation method and clearing fields definition. Also clean some fields definition inconsistencies, notably required fields that should instead be correctly computed or default that have no real meaning. SPECIFICATIONS: REQUIRED FIELDS As computed fields are computed after create required attribute cannot be respected without computing them beforehand. That is why we have some custom code to compute required fields if not given at create and update the creation values accordingly. SPECIFICATIONS: MAIL SCHEDULING Mail scheduling on event type is modified in this commit. Previously checking the use_mail_schedule radio button had no effect on event_type_mail_ids field. It is now reset if unchecked. It is therefore coherent with use_ticket and event_type_ticket_ids field behavior. LINKS Task ID 2089156 Community PR odoo/odoo#42911 Co-Authored-By: Thibault Delavallée <tde@odoo.com> Co-Authored-By: Michaël Mattiello <mcm@odoo.com>
2020-02-04[IMP] event: change name field from event registration + minor changesPatrick Hoste
PURPOSE Make 'name' field from event registration mandatory. Change placeholder for event name to give an example. LINKS Task ID : 2093336 PR : #43420
2020-01-28[IMP] event(_sale): add some tests before updating modelsThibault Delavallée
As some event models (event.type and event.ticket notably) are about to be modified let us add some tests to avoid regressions. Security tests are also moved in their own file. Some internals tests defined in event_sale are also moved in their own file. That way we avoid bloating files with unrelated tests. Future commits will add tests for event and event.type models. LINKS Task ID 2177281 (support tickets directly in event) Prepares Community PR odoo/odoo#43488 Closes Community PR odoo/odoo#44066