summaryrefslogtreecommitdiff
path: root/addons/web_editor/static/src/js/widgets/widgets.js
diff options
context:
space:
mode:
authorThibault Delavallée <tde@odoo.com>2018-04-09 15:33:51 +0200
committerThibault Delavallée <tde@odoo.com>2018-04-09 16:52:12 +0200
commit3bb498d696744c36b198c4da7cf428d643699aff (patch)
treef4ca3440fafa985ddf34c02c68a15690bf4f0f35 /addons/web_editor/static/src/js/widgets/widgets.js
parent7c936c68f98239fad8fe06a488e8438f4c0509df (diff)
[REVERT] "[IMP] core: tolerate a 10% deviation for number of queries"
This reverts commit d565596868a55b5e593d2907b0cfba66c5daefac. Indeed whole purpose of having tests based on query counters is to fail every time query count is greater than expected. Query count could be greater than expected because * either it is required by a bug fix or a feature and tests should be updated accordingly in the same commit; * either implementation can be improved to avoid or lessen query count impact and code should be updated accordingly; * either we have some random queries due to nondeterministic behavior; It seems purpose of the commit was to solve the third case. However we think hiding first two cases can be dangerous compared to solving third case. Moreover having a threshold of 10% does not make sense. It means some complex test case could take 30 queries more without being noticed. Some tests could fail after several commits adding queries and finding them afterwards could be complicated. Another solution based on flagging some tests that have a small random behavior will come soon.
Diffstat (limited to 'addons/web_editor/static/src/js/widgets/widgets.js')
0 files changed, 0 insertions, 0 deletions