Odoo/addons/event/tests, branch 14.0 The current checkout of upstream Odoo [IMP] event, mail, mass_mailing, sms, test_mail: clean some mail tests tools helpers and parameters 2021-04-08T15:06:12+00:00 Thibault Delavallée tde@odoo.com 2021-04-07T09:17:19+00:00 c75e8619663efc4d97ab13fb35f815104239dd36 In this commit we backport some of 14.1+ improvements done in mail tools in order to keep a coherent definition through sub versions. We also improve docstring and add some explanations on available toold and asserts. Task ID-2500615 COM PR odoo/odoo#68874 
In this commit we backport some of 14.1+ improvements done in mail tools
in order to keep a coherent definition through sub versions. We also
improve docstring and add some explanations on available toold and asserts.

Task ID-2500615
COM PR odoo/odoo#68874
 [FIX] event: respect scheduled date when calling mail schedulers execute 2021-03-19T16:36:25+00:00 Thibault Delavallée tde@odoo.com 2021-03-19T13:30:15+00:00 353bc5de9fafbc1527c382614e02438ee799c8a4 In this commit we ensure calling ``execute`` method on communication schedulers do not send emails or SMS if their scheduled date is still not achieved. Currently only the cron method does it (see ``run``). It is now safe to call ``execute`` directly on event communication schedulers. Related to Task ID-2414658 COM PR odoo/odoo#68158 
In this commit we ensure calling ``execute`` method on communication schedulers
do not send emails or SMS if their scheduled date is still not achieved.
Currently only the cron method does it (see ``run``).

It is now safe to call ``execute`` directly on event communication schedulers.

Related to Task ID-2414658
COM PR odoo/odoo#68158
 [FIX] event: allow event user to confirm registrations even with mail schedulers 2021-03-19T16:36:23+00:00 Thibault Delavallée tde@odoo.com 2021-03-19T13:24:26+00:00 73d09268922a7d242af85e36a3d81ed25ab4ca33 Due to ACLs it is currently impossible for event users to confirm a draft registration if schedulers are involved. Indeed it implies updating the scheduler which is not do-able for them. In this commit we sudo the update of schedulers, as this is a technical object and access is granted through registrations. Related to Task ID-2414658 COM PR odoo/odoo#68158 
Due to ACLs it is currently impossible for event users to confirm a draft
registration if schedulers are involved. Indeed it implies updating the
scheduler which is not do-able for them.

In this commit we sudo the update of schedulers, as this is a technical
object and access is granted through registrations.

Related to Task ID-2414658
COM PR odoo/odoo#68158
 [IMP] event: improve tests about communication scheduling 2021-03-19T16:36:20+00:00 Thibault Delavallée tde@odoo.com 2021-03-19T13:31:59+00:00 1a66d9cb57dc17b697b7a56effa91de3a4b50bd7 In this commit we improve event communication scheduling tests. We make tests more detailed and use mail tools to ensure content. We also check scheduled dates and use freezegun to ease date management. Related to Task ID-2414658 COM PR odoo/odoo#68158 
In this commit we improve event communication scheduling tests. We make tests
more detailed and use mail tools to ensure content. We also check scheduled
dates and use freezegun to ease date management.

Related to Task ID-2414658
COM PR odoo/odoo#68158
 [FIX] event: split stored editable computed fields compute method 2021-02-10T16:56:13+00:00 Thibault Delavallée tde@odoo.com 2021-02-08T09:34:29+00:00 1b59fe9aeb2e853b502b494344c57a194a8c0c3e RATIONALE Stored editable fields receive their values either from compute either from user input. If a user input is given to create / write compute method is not called. If multiple fields are computed through the same method giving one field value discard call to compute method and other fields are not called. SPECIFICATIONS Split ``_compute_contact_info`` compute method so that partner related fields are independent. LINKS COM PR #65688 Task ID-2455165 
RATIONALE

Stored editable fields receive their values either from compute either from
user input. If a user input is given to create / write compute method is not
called. If multiple fields are computed through the same method giving one
field value discard call to compute method and other fields are not called.

SPECIFICATIONS

Split ``_compute_contact_info`` compute method so that partner related fields
are independent.

LINKS

COM PR #65688
Task ID-2455165
 [IMP] event, website_event_track: add tests about stored editable computed fields 2021-02-10T16:56:07+00:00 Thibault Delavallée tde@odoo.com 2021-02-08T10:24:44+00:00 6eac6ede401fd949405b7e1c8c82acfa5a3f6a9d Add tests related to registration / partner contact fields synchronization. Add tests with user input and/or partner synchronization to ensure editable stored fields work as expected on registration model. Add tests related to event track / partner contact fields synchronization. Add tests with user input and/or partner synchronization to ensure editable stored fields work as expected on track model. Add tests related to event / event type configuration fields synchronization. Add tests with user input and/or event type synchronization to ensure editable stored fields work as expected on event model. Warning: those tests are currently partly failing. Next commits will split computed fields into several methods in order to fix computation. LINKS COM PR #65688 Task ID-2455165 
Add tests related to registration / partner contact fields synchronization.
Add tests with user input and/or partner synchronization to ensure editable
stored fields work as expected on registration model.

Add tests related to event track / partner contact fields synchronization.
Add tests with user input and/or partner synchronization to ensure editable
stored fields work as expected on track model.

Add tests related to event / event type configuration fields synchronization.
Add tests with user input and/or event type synchronization to ensure editable
stored fields work as expected on event model.

Warning: those tests are currently partly failing. Next commits will split
computed fields into several methods in order to fix computation.

LINKS

COM PR #65688
Task ID-2455165
 [FIX] event: make ticket sale start date inclusive 2020-12-17T11:03:15+00:00 Aurélien Warnon awa@odoo.com 2020-12-17T11:03:15+00:00 ea6952fd7ec881b79a7294c40427ce9966997e66 This commit fixes the ticket sale start date to be considered inclusive. Indeed, before this commit, if the sales of a ticket starts on the 1st of December, people arriving on the website at that exact date will NOT be able to buy tickets although they should be. They will have to wait for the next day to be able to buy tickets. A small test was added to ensure this behavior. Task 2415917 closes odoo/odoo#63512 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> 
This commit fixes the ticket sale start date to be considered inclusive.

Indeed, before this commit, if the sales of a ticket starts on the 1st of
December, people arriving on the website at that exact date will NOT be able to
buy tickets although they should be. They will have to wait for the next day to
be able to buy tickets.

A small test was added to ensure this behavior.

Task 2415917

closes odoo/odoo#63512

Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
[FIX] website_event(_*): improve user flow and experience from frontend 2020-08-17T16:29:49+00:00 std-odoo std@odoo.com 2020-08-13T12:38:02+00:00 3dfb3c1e747bf8b78a20acff314212eca2f22998 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 
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
 [FIX] event(_questions): take better care of 2many fields when updating from event type 2020-06-16T09:14:31+00:00 Sébastien Mottet (oms) oms@odoo.com 2020-04-27T14:37:02+00:00 be11161a42947437447c5aba699f558a12589c0d PURPOSE Fix various issues spotted in 13.3 when testing event. Notably computation of 2many fields coming from template. SPECIFICATIONS When updating template on an event, one2many fields should be better managed. Previous heuristic was * if event type uses o2m configuration (use_ticket / _schedule / _question) and has lines * erase existing lines; * create new lines based on old one; This has the drawback of loosing information of what is sent (mail) or sold (tickets) or answered( questions). Another drawback is that only types having line are synchronized. This means that if updating several times the event type you could end up with an XMas configuration with lines coming from different event types, depending on their o2m configuration. We choose a better heuristic that should solve this issue * every time we change type, independently of its use_* field that is used mainly for UX on the type itself: * erase existing lines that have not been used yet (no mail sent, no ticket linked to registrations, no answer linked to registrations) * create new lines based on old one; if type has no lines, event will have its old empty line erased as well; It means that we try to synchronize more the type to the event while keeping configuration line already used in some registrations. Also provide some other fixes like deletion restrictions or better domain for UX purpose. See sub commits for more details. LINKS Task ID 2244487 PR odoo/odoo#52998 FwdPort of odoo/odoo#52923 X-original-commit: 645f70cad033083e82a3ef9102c694c331badef9 Co-authored-by: Sebastien Mottet <oms@odoo.com> Co-authored-by: Thibault Delavallée <tde@odoo.com> 
PURPOSE

Fix various issues spotted in 13.3 when testing event. Notably
computation of 2many fields coming from template.

SPECIFICATIONS

When updating template on an event, one2many fields should be better managed.
Previous heuristic was

  * if event type uses o2m configuration (use_ticket / _schedule / _question)
    and has lines

   * erase existing lines;
   * create new lines based on old one;

This has the drawback of loosing information of what is sent (mail) or
sold (tickets) or answered( questions). Another drawback is that only
types having line are synchronized. This means that if updating several
times the event type you could end up with an XMas configuration with
lines coming from different event types, depending on their o2m configuration.

We choose a better heuristic that should solve this issue

  * every time we change type, independently of its use_* field that is used
    mainly for UX on the type itself:

    * erase existing lines that have not been used yet (no mail sent, no
      ticket linked to registrations, no answer linked to registrations)
    * create new lines based on old one; if type has no lines, event will
      have its old empty line erased as well;

It means that we try to synchronize more the type to the event while keeping
configuration line already used in some registrations.

Also provide some other fixes like deletion restrictions or better domain
for UX purpose. See sub commits for more details.

LINKS

Task ID 2244487
PR odoo/odoo#52998
FwdPort of odoo/odoo#52923

X-original-commit: 645f70cad033083e82a3ef9102c694c331badef9
Co-authored-by: Sebastien Mottet <oms@odoo.com>
Co-authored-by: Thibault Delavallée <tde@odoo.com>
 [IMP] event: improve some type -> event configuration tests 2020-06-16T09:14:31+00:00 Thibault Delavallée tde@odoo.com 2020-06-12T13:34:47+00:00 7c37d457e7ff9261bf17deec25213bab8e56d1fc Purpose of this commit is to add some tests related to event_type to event configuration. Indeed changing a type on an event may change its sub models (mails, tickets, questions). Asserting current behavior is necessary before tweaking behavior considered as to be improved. Task ID 2244487 PR odoo/odoo#52998 FwdPort of odoo/odoo#52923 X-original-commit: 6fb42e70164bab05681b11f1e76e320db0266445 
Purpose of this commit is to add some tests related to event_type to event
configuration. Indeed changing a type on an event may change its sub models
(mails, tickets, questions). Asserting current behavior is necessary before
tweaking behavior considered as to be improved.

Task ID 2244487
PR odoo/odoo#52998
FwdPort of odoo/odoo#52923

X-original-commit: 6fb42e70164bab05681b11f1e76e320db0266445