Odoo/addons/gamification/tests/__init__.py, branch 14.0 The current checkout of upstream Odoo [IMP] gamification: merge karma related tests in the same file and improve rank tests 2019-11-05T15:08:34+00:00 Thibault Delavallée tde@odoo.com 2019-11-05T15:01:03+00:00 c5b7e000656d8872d434e37517b0c6d9d29ffe05 Purpose is to have all karma related tests in the same file to ease finding them back. Some tweaking is also done like using a savepoint case and ensuring tests can always be re-run. LINKS Task ID 2003505 PR #34594 
Purpose is to have all karma related tests in the same file to ease finding
them back. Some tweaking is also done like using a savepoint case and ensuring
tests can always be re-run.

LINKS

Task ID 2003505
PR #34594
 [IMP] gamification: track karma change on users 2019-11-05T15:08:34+00:00 Patrick Hoste pko@odoo.com 2019-06-27T07:54:04+00:00 bfbc7c6a184b2b507b1bf4ad778430bc2f3a0e7f PURPOSE Allow karma gain tracking enabling notably display of top users based on weekly / monthly gain in website profile. SPECIFCIATIONS Each time a user gains karma a record is created in the gamification karma tracking model. Scheduled activity runs to consolidate the records into monthly gain records to avoid having crowdy table and unnecessary noise in karma gain. This model is made private and only accessible through some dedicated compute methods / controllers used in website profile. In website profile module buttons are added to see users ranking based on their total karma (like before) but also by last week and last month gains (using the newly introduced tracking model). LINKS Task ID 2003505 PR #34594 
PURPOSE

Allow karma gain tracking enabling notably display of top users based on
weekly / monthly gain in website profile.

SPECIFCIATIONS

Each time a user gains karma a record is created in the gamification karma
tracking model. Scheduled activity runs to consolidate the records into
monthly gain records to avoid having crowdy table and unnecessary noise
in karma gain.

This model is made private and only accessible through some dedicated
compute methods / controllers used in website profile.

In website profile module buttons are added to see users ranking based
on their total karma (like before) but also by last week and last month
gains (using the newly introduced tracking model).

LINKS

Task ID 2003505
PR #34594
 [FIX] gamification: perf on write karma_min on gamification.karma.rank 2019-07-24T09:03:13+00:00 Jeremy Kersten jke@odoo.com 2019-07-11T17:00:30+00:00 8a80efd7cd9f564338c6ca6c72e49f6890190b4c This commits avoid to call recompute when you write on the rank without touch the karma_min value. On write on karma_min, we have 2 cases: - Rank order are the same, just need to recompute the rank for the user that could be impacted. Eg. if karma_min changes from 45 to 50, we need to recheck for all user between 45 and 50 their new rank. - Rank order are not the same, we need to recompute for all users. (could be still improved if needed) When you recompute the rank on a list of users, depending of the number of users (bulk if more than 3 * number of rank) we check for each user what is the new rank, or for each rank whats is the new users. task-internal No way to edit a rank on the prod server. Lock sql -> crash server closes odoo/odoo#34835 Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com> 
This commits avoid to call recompute when you write on the rank without
touch the karma_min value.

On write on karma_min, we have 2 cases:
- Rank order are the same, just need to recompute the rank for the user
that could be impacted. Eg. if karma_min changes from 45 to 50, we need
to recheck for all user between 45 and 50 their new rank.
- Rank order are not the same, we need to recompute for all users.
(could be still improved if needed)

When you recompute the rank on a list of users, depending of the number of
users (bulk if more than 3 * number of rank) we check for each user what is
the new rank, or for each rank whats is the new users.

task-internal

No way to edit a rank on the prod server. Lock sql -> crash server

closes odoo/odoo#34835

Signed-off-by: Jérémy Kersten (jke) <jke@openerp.com>
 [LEGAL] Use global LICENSE/COPYRIGHT files, remove boilerplate text 2015-06-02T01:16:04+00:00 Olivier Dony odo@openerp.com 2015-06-01T22:39:30+00:00 0bd454534818941bc3216025ebe3dcac3d78c19d - Preserved explicit 3rd-party copyright notices - Explicit boilerplate should not be necessary - copyright law applies automatically in all countries thanks to Berne Convention + WTO rules, and a reference to the applicable license is clear enough. 
- Preserved explicit 3rd-party copyright notices
- Explicit boilerplate should not be necessary - copyright law applies
  automatically in all countries thanks to Berne Convention + WTO rules,
  and a reference to the applicable license is clear enough.
[FIX] remove deprecated checks/fast_suite test attributes from standard modules 2015-01-15T13:31:40+00:00 Xavier Morel xmo@odoo.com 2015-01-15T13:30:16+00:00 65cd4a2a330e8ed4134af3bbb3b015600bfffcc3 






[REF] gamification: python tests and other improvements
2013-12-18T11:12:43+00:00

Martin Trigaux
mat@openerp.com

2013-12-18T11:12:43+00:00

e7887b8b8f892832c5b65b82358d022496a2729d

bzr revid: mat@openerp.com-20131218111243-npnauv6mxhb4nttg




bzr revid: mat@openerp.com-20131218111243-npnauv6mxhb4nttg